git-auto-commit-action/README.md

161 lines
6.0 KiB
Markdown
Raw Normal View History

# git-auto-commit Action
2019-06-10 12:30:57 +00:00
2020-05-05 22:00:33 +00:00
> The GitHub Action for committing files for the 80% use case.
2019-06-10 13:32:16 +00:00
This GitHub Action automatically commits files which have been changed during a Workflow run and pushes the commit back to GitHub.
The default committer is "GitHub Actions <actions@github.com>", and the default author of the commit is "Your GitHub Username <github_username@users.noreply.github.com>".
2019-06-10 13:32:16 +00:00
This Action has been inspired and adapted from the [auto-commit](https://github.com/cds-snc/github-actions/tree/master/auto-commit
2020-01-11 20:32:17 +00:00
)-Action of the Canadian Digital Service and this [commit](https://github.com/elstudio/actions-js-build/blob/41d604d6e73d632e22eac40df8cc69b5added04b/commit/entrypoint.sh)-Action by Eric Johnson.
2019-06-10 13:32:16 +00:00
## Usage
2020-05-05 22:00:33 +00:00
Add the following step at the end of your job, after other steps that might add or change files.
2019-08-20 19:05:10 +00:00
```yaml
2020-04-28 11:28:19 +00:00
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
2019-08-20 19:05:10 +00:00
with:
# Required
2019-08-20 19:05:10 +00:00
commit_message: Apply automatic changes
2020-02-06 19:49:03 +00:00
# Optional name of the branch the commit should be pushed to
# Required for almost all non-`push` events, eg. `pull_request`, `schedule`
2019-09-20 18:26:41 +00:00
branch: ${{ github.head_ref }}
2019-10-25 20:18:32 +00:00
# Optional git params
commit_options: '--no-verify --signoff'
2019-10-25 20:18:32 +00:00
# Optional glob pattern of files which should be added to the commit
2020-04-23 18:46:41 +00:00
file_pattern: src/*.js tests/*.js
2020-02-05 19:24:25 +00:00
# Optional local file path to the repository
repository: .
2020-02-05 19:24:25 +00:00
# Optional commit user and author settings
commit_user_name: My GitHub Actions Bot
commit_user_email: my-github-actions-bot@example.org
2020-03-13 11:35:11 +00:00
commit_author: Author <actions@github.com>
2020-03-05 19:31:06 +00:00
# Optional tag message
# Action will create and push a new tag to the remote repository and the defined branch
2020-03-05 19:31:06 +00:00
tagging_message: 'v1.0.0'
2019-08-20 19:05:10 +00:00
```
2020-05-05 22:00:33 +00:00
## Example
In this example, we're running `php-cs-fixer` in a PHP project to fix the codestyle automatically,
then commit possible changed files back to the repository.
Note that we explicitly specify `${{ github.head_ref }}` in both the checkout and the commit Action.
This is required in order to work with the `pull_request` event (or any other non-`push` event).
```yaml
name: php-cs-fixer
on:
pull_request:
push:
branches:
- "master"
jobs:
php-cs-fixer:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
with:
ref: ${{ github.head_ref }}
- name: Run php-cs-fixer
uses: docker://oskarstark/php-cs-fixer-ga
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
with:
commit_message: Apply php-cs-fixer changes
branch: ${{ github.head_ref }}
```
2019-08-20 19:05:10 +00:00
## Limitations & Gotchas
2019-09-22 12:52:33 +00:00
### Checkout the correct branch
2019-08-31 16:43:23 +00:00
You must use `action/checkout@v2` or later versions to checkout the repository.
In non-`push` events, such as `pull_request`, make sure to specify the `ref` to checkout:
```yaml
- uses: actions/checkout@v2
with:
ref: ${{ github.head_ref }}
```
2019-08-31 16:43:23 +00:00
### Specify the branch name
2019-08-31 16:43:23 +00:00
It is highly recommended to always specify the `branch` option explicitly.
While the default setting works for `push` events, other events such as `pull_request` require it to work correctly.
2020-02-23 10:29:03 +00:00
2020-05-05 22:21:35 +00:00
```yaml
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
with:
commit_message: Some automated code change
branch: ${{ github.head_ref }}
```
This Action does not contain magic and can't easily determine to which branch a commit should be pushed to. 🔮.
### Commits of this Action do not trigger new Workflow runs
The resulting commit **will not trigger** another GitHub Actions Workflow run.
This is due to [limititations set by GitHub](https://help.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token).
> When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.
You can change this by creating a new [Personal Access Token (PAT)](https://github.com/settings/tokens/new),
storing the token as a secret in your repository and then passing the new token to the [`actions/checkout`](https://github.com/actions/checkout#usage) Action.
2020-04-24 08:14:37 +00:00
2020-01-11 20:32:11 +00:00
```yaml
- uses: actions/checkout@v2
with:
token: ${{ secrets.PAT_TOKEN }}
```
2020-01-11 20:32:11 +00:00
### Unable to commit into PRs from forks
2020-01-11 20:32:11 +00:00
GitHub currently prohibits Actions like this to push commits to forks, even when they created a PR and allow edits.
See [issue #25](https://github.com/stefanzweifel/git-auto-commit-action/issues/25) for more information.
2020-01-11 20:32:11 +00:00
## Inputs
2019-10-25 20:18:32 +00:00
2019-11-04 19:09:04 +00:00
Checkout [`action.yml`](https://github.com/stefanzweifel/git-auto-commit-action/blob/master/action.yml) for a full list of supported inputs.
2019-10-25 20:18:32 +00:00
2020-03-04 19:33:10 +00:00
## Outputs
2020-03-04 19:33:10 +00:00
You can use these outputs to trigger other Actions in your Workflow run based on the result of `git-auto-commit-action`.
- `changes_detected`: Returns either "true" or "false" if the repository was dirty and files have changed.
2020-02-04 18:37:00 +00:00
## Troubleshooting
### Action does not push commit to repository
Make sure to [checkout the correct branch](#checkout-the-correct-branch) and [specify the branch name](#specify-the-branch-name).
### Action does not push commit to repository: Authentication Issue
2020-02-23 10:42:57 +00:00
If your Workflow can't push the commit to the repository because of authentication issues,
please update your Workflow configuration and usage of [`actions/checkout`](https://github.com/actions/checkout#usage).
2020-02-23 10:42:57 +00:00
Updating the `token` value with a Personal Access Token should fix your issues.
2020-02-23 10:42:57 +00:00
### No new workflows are triggered by the commit of this action
2020-01-11 20:32:17 +00:00
This is due to limitations set up by GitHub, [commits of this Action do not trigger new Workflow runs](#commits-of-this-action-do-not-trigger-new-workflow-runs).
2020-01-11 20:32:17 +00:00
2019-06-10 13:32:16 +00:00
## Versioning
We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/stefanzweifel/git-auto-commit-action/tags).
## License
This project is licensed under the MIT License - see the [LICENSE](https://github.com/stefanzweifel/git-auto-commit-action/blob/master/LICENSE) file for details.