Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(action): trust-check/verify-signatures - Verify commit signatures

Open
#41 0 comments 0 reactions 1 assignee View on GitHub

@aRustyDev is already working on this.

Since Jan 27, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement new-action

Parent Epic

Part of #22 (Atomic Release Pipeline Actions)

Priority

P2 - Trust validation for secure release pipelines

Description

Create a composite action that verifies commit signatures in a range.

Inputs

Input Required Default Description
commit-range No HEAD~1..HEAD Commit range to verify
require-all No true Require all commits to be signed
allowed-keys No - Allowed GPG key IDs (comma-separated)
verify-github No true Accept GitHub's web-flow signature

Outputs

Output Description
all-signed "true" if all commits are signed
signed-count Number of signed commits
unsigned-count Number of unsigned commits
unsigned-commits Comma-separated list of unsigned commit SHAs

Usage Example

- uses: arustydev/gha/actions/trust-check/verify-signatures@v1
  id: signatures
  with:
    commit-range: "origin/main..HEAD"
    require-all: true

- if: steps.signatures.outputs.all-signed != 'true'
  run: |
    echo "Unsigned commits: ${{ steps.signatures.outputs.unsigned-commits }}"
    exit 1

Implementation Notes

  • Uses git verify-commit for verification
  • Handles GitHub's web-flow GPG key
  • Supports allowlist of specific GPG keys
  • Reports detailed results per commit

Source Reference

helm-charts/.github/workflows/auto-merge-integration.yaml:

  • Signature verification logic for trusted merges
Dominant language
Shell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.