actions-marketplace-validations/GitHub Action for committing changes to repository
Powerful GitHub Action for automatically committing and pushing changes back to your repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Personal Access Token for GitHub for pushing the code | yes | "" |
| add_timestamp | Whether to add timestamp to a new branch name | no | false |
| amend | Whether to make amendment to the previous commit (--amend). Can be combined with commit_message to change the message. | no | false |
| commit_prefix | Prefix added to commit message | no | "" |
| commit_message | Commit message to set | no | "" |
| force | Whether to use force push (--force). Use only when you need to overwrite remote changes. Potentially dangerous. | no | false |
| force_with_lease | Whether to use force push with lease (--force-with-lease). Safer than force as it checks for remote changes. | no | false |
| no_edit | Whether to not edit commit message when using amend | no | false |
| organization_domain | Name of GitHub Enterprise organization | no | github.com |
| target_branch | Name of a new branch to push the code into (skipped when no changes and amend is false) | no | "" |
Outputs
| name | description |
|---|---|
| files_changed | List of changed files |
| branch_name | Name of the branch code was pushed into |