magmanu/github-actions-bot-signed-commit

Sign commits using GitHub App or GITHUB_TOKEN. Compatible with large and binary files.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Maintainedlast commit Dec 11, 2025
License
None

Pinned Snippet

workflow.ymlSHA-pinned
uses: magmanu/github-action-bot-signed-commit@fb2582c7c22a7183a95504156c4ac02bb734d6ed # v1.0.4

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
TOKENIf signing commits with Github Apps, provide the App token. Else, it defults to GITHUB_TOKEN.no${{ github.token }}
TARGET_OWNERThe repository owner (user/org)no${{ github.repository_owner }}
TARGET_REPOThe repository where the signed commits will be pushed to.no${{ github.event.repository.name }}
TARGET_REFThe branch where the signed commits will be pushed to.no${{ github.head_ref || github.ref_name }}
FILE_LISTAbsolute path to a text file containing the list of file paths to be committed.yes
WORKING_DIRThe absolute path for the working directory where the action will run.no${{ github.workspace }}
IS_DRY_RUNIf set to true, the action will push the commits but leave them orphans (the head won't move.)nofalse
SHOULD_CREATE_NEW_BRANCHIf set to true, the action will create the target branch if it doesn't exist.notrue
COMMIT_MESSAGEThe commit message to use for the signed commits. Your message will be suffixed with a UTC human-friendly timestamp.noSigned commit
namedescription
shaSHA of the verified commit