chillicream/Create Signed Commit
Create a server-signed (verified) commit via the GitHub Git Data API using a pre-minted GitHub App installation token.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Apr 26, 2026
- License
- MIT
Pinned Snippet
uses: chillicream/create-signed-commit@75b38ccd01b93548dd2fa458e533b62015ecf35c # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | GitHub App installation token (e.g. from actions/create-github-app-token). Needs `contents: write`. | yes | — |
| commit_message | Commit message headline. | yes | — |
| branch | Target branch. Defaults to GITHUB_HEAD_REF or GITHUB_REF_NAME. | no | "" |
| repository | Target repository in `owner/repo` form. Defaults to GITHUB_REPOSITORY. | no | "" |
| files | Newline-separated list of paths to commit. If empty, paths are discovered with `git ls-files --modified --others --exclude-standard`. Missing paths are committed as deletions. | no | "" |
| working_directory | Working directory for git commands. Defaults to the workflow workspace. | no | "" |
Outputs
| name | description |
|---|---|
| sha | SHA of the created commit. Empty when there are no changes. |