2019-06-10 20:30:57 +08:00
# git-auto-commit-action
2019-06-10 21:32:16 +08:00
This GitHub Action automatically commits files which have been changed during a Workflow run and pushes the Commit back to GitHub.
2019-09-01 00:43:23 +08:00
The Committer is "GitHub Actions < actions @ github . com > " and the Author of the Commit can be configured with input variables.
2019-06-10 21:32:16 +08:00
If no changes are available, the Actions does nothing.
This Action has been inspired and adapted from the [auto-commit](https://github.com/cds-snc/github-actions/tree/master/auto-commit
2019-09-01 00:43:23 +08:00
)-Action of the Canadian Digital Service and the [commit ](https://github.com/elstudio/actions-js-build/blob/41d604d6e73d632e22eac40df8cc69b5added04b/commit/entrypoint.sh )-Action by Eric Johnson.
2019-06-10 21:32:16 +08:00
## Usage
2019-09-01 00:43:23 +08:00
Add the following step at the end of your job.
2019-08-21 03:05:10 +08:00
```yaml
- uses: stefanzweifel/git-auto-commit-action@dev
with:
commit_author_email: john.doe@example.com
commit_author_name: John Doe
commit_message: Apply automatic changes
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
2019-09-01 00:43:23 +08:00
The Action will only commit files back, if changes are available. The resulting commit **will not trigger** another GitHub Actions Workflow run!
2019-08-21 03:05:10 +08:00
2019-06-10 21:32:16 +08:00
2019-09-01 00:43:23 +08:00
### Inputs
2019-06-10 21:32:16 +08:00
2019-08-21 03:05:10 +08:00
The following inputs are required
2019-06-10 21:32:16 +08:00
2019-09-06 13:19:37 +08:00
- `commit_author_email` : The Commit Authors Email Address
- `commit_author_name` : The Commit Authors Name
- `commit_message` : The commit message used when changes are available
2019-06-10 21:32:16 +08:00
2019-09-01 00:43:23 +08:00
### Environment Variables
The `GITHUB_TOKEN` secret is required. It is automatically available in your repository. You have to add it to the configuration though.
## Example Usage
This Action will only work, if the job in your workflow changes project files.
The most common use case for this, is when you're running a Linter or Code-Style fixer on GitHub Actions.
In this example I'm running `php-cs-fixer` in a PHP project.
```yaml
on: push
name: php-cs-fixer
jobs:
php-cs-fixer:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
with:
fetch-depth: 1
- name: Run php-cs-fixer
uses: docker://oskarstark/php-cs-fixer-ga
- name: Commit changed files
uses: stefanzweifel/git-auto-commit-action@v2.0.0
with:
commit_author_email: hello@stefanzweifel.io
commit_author_name: Stefan Zweifel
commit_message: Apply php-cs-fixer changes
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```
2019-06-10 21:32:16 +08: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.