hituzi-no-sippo/Commit changed files with ghcp
Commit changed files with ghcp. - Tagret Repository The repository running the action - Tagret branch The branch running the action Requires a GitHub token. The GitHub token used depends on whether `inputs.github_token` is inputed. - Input `inputs.github_token` Use `inputs.github_token`. ```YAML - uses: hituzi-no-sippo/commit-changed-files-with-ghcp-action@v1.0.0 with: files: README.md commit_message: "docs: add README" github_token: <GITHUB_TOKEN> ``` - Does not input `inputs.github_token` Generate a GitHub token with GitHub app. Use `inputs.github_app_id` and `inputs.github_app_private_key`. ```YAML - uses: hituzi-no-sippo/commit-changed-files-with-ghcp-action@v1.0.0 with: files: README.md commit_message: "docs: add README" github_app_id: <GITHUB_APP_ID> github_app_private_key: <GITHUB_APP_PRIVATE_KEY> ``` GitHub token generated with GitHub app triggers GitHub Actions workflow. `secrets.GITHUB_TOKEN` does not trigger GitHub Actions workflow. https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow > When you use the repository's `GITHUB_TOKEN` to perform tasks, > events triggered by the `GITHUB_TOKEN`, > with the exception of `workflow_dispatch` and `repository_dispatch`, > will not create a new workflow run.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Oct 27, 2023
- License
- None
Pinned Snippet
uses: hituzi-no-sippo/commit-changed-files-with-ghcp-action@1b988555abcc0b8591a9b489ed074bf5ac67eaa6 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| commit_message | Message of commit | yes | — |
| github_token | GitHub token is used on commit. If use `secrets.GITHUB_TOKEN`, add `write` access of contents. This is because to commit need to `write` access of contents. ```YAML jobs: commit: name: commit permissions: contents: write ``` - https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token - https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions - https://docs.github.com/en/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#repository-permissions-for-contents | no | — |
| github_app_id | GitHub app ID to generate GitHub token. Generated GitHub token is used on commit. The GitHub app of `secrets.github_app_id` and `secrets.github_app_private_key` requires `Read and write` access of contents. This is because this workflow create commit. References - https://docs.github.com/en/apps/creating-github-apps/registering-a-github-app/choosing-permissions-for-a-github-app - https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps#generating-private-keys - https://docs.github.com/en/rest/overview/permissions-required-for-github-apps#repository-permissions-for-contents | no | — |
| github_app_private_key | GitHub app private key to generate GitHub token. Generated GitHub token is used on commit. | no | — |
Outputs
no outputs