git-auto-commit-action/README.md

166 lines
6.2 KiB
Markdown
Raw Normal View History

2019-06-10 12:30:57 +00:00
# git-auto-commit-action
2020-02-05 19:27:14 +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
2020-02-04 18:37:00 +00:00
If no changes are detected, the Action does nothing.
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
2020-02-04 18:37:00 +00:00
*This Action currently can't be used in conjunction with pull requests of forks. See [issue #25](https://github.com/stefanzweifel/git-auto-commit-action/issues/25) for more information.*
2020-01-04 16:54:44 +00:00
2019-06-10 13:32:16 +00:00
## Usage
2020-02-04 18:42:37 +00:00
**Note:** This Action requires that you use `action/checkout@v2` or above to checkout your repository.
2020-02-04 18:37:00 +00:00
2019-08-31 16:43:23 +00:00
Add the following step at the end of your job.
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:
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 if Action is used in Workflow listening to the `pull_request` event
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
2020-03-05 19:48:00 +00:00
# Optional tag message. Will create and push a new tag to the remote repository
2020-03-05 19:31:06 +00:00
tagging_message: 'v1.0.0'
2019-08-20 19:05:10 +00:00
```
2019-08-31 16:43:23 +00: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-20 19:05:10 +00:00
2020-02-23 10:29:03 +00:00
We recommend to use this Action in Workflows, which listen to the `pull_request` event. You can then use the option `branch: ${{ github.head_ref }}` to set up the branch name correctly.
2020-02-29 08:52:12 +00:00
If you don't pass a branch name, the Action will try to push the commit to a branch with the same name, as with which the repo has been checked out.
2019-09-22 12:52:33 +00:00
2019-08-31 16:43:23 +00:00
## Example Usage
2020-02-23 10:29:03 +00:00
This Action will only work, if the job in your Workflow changes files.
2019-08-31 16:43:23 +00:00
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.
2020-02-23 10:29:03 +00:00
### Example on `pull_request` event
2020-04-24 08:14:37 +00:00
If you would like to use this Action in a Workflow which listens to the `pull_request` event, you must add the `ref`-input to the `actions/checkout@v2` step. It's also recommended to add the `branch`-input to the `git-auto-commit`-step. This way you tell the Action exactly where to push the commit.
2020-01-11 20:32:11 +00:00
```yaml
name: php-cs-fixer
on: pull_request
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
2020-04-28 11:28:19 +00:00
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
2020-01-11 20:32:11 +00:00
with:
commit_message: Apply php-cs-fixer changes
branch: ${{ github.head_ref }}
2019-08-31 16:43:23 +00:00
```
2019-06-10 13:32:16 +00:00
2020-02-23 10:29:03 +00:00
### Example on `push` event
2020-02-06 19:49:03 +00:00
```yaml
name: php-cs-fixer
on: push
jobs:
php-cs-fixer:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Run php-cs-fixer
uses: docker://oskarstark/php-cs-fixer-ga
2020-04-28 11:28:19 +00:00
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
2020-02-06 19:49:03 +00:00
with:
commit_message: Apply php-cs-fixer changes
```
2019-10-25 20:18:32 +00:00
### Inputs
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
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
2020-02-23 10:29:03 +00:00
### Can't push commit to repository
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). (Updating the `token` value with a Personal Access Token should fix your issues)
### Commit of this Action does not trigger a new Workflow run
2020-03-13 11:35:11 +00:00
As mentioned in the [Usage](#Usage) section, the commit created by this Action **will not trigger** a new Workflow run automatically.
2020-02-23 10:29:03 +00:00
This is due to limitations set up by GitHub:
> An action in a workflow run can't trigger a new workflow run. For example, if an action pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
[Source](https://help.github.com/en/actions/reference/events-that-trigger-workflows)
2020-03-17 12:44:47 +00:00
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-02-04 18:37:00 +00:00
2020-02-23 10:42:57 +00:00
#### Example Workflow
```yaml
name: php-cs-fixer
on: push
jobs:
php-cs-fixer:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
2020-03-03 11:08:03 +00:00
with:
token: ${{ secrets.PAT_TOKEN }}
2020-02-23 10:42:57 +00:00
- name: Run php-cs-fixer
uses: docker://oskarstark/php-cs-fixer-ga
2020-04-28 11:28:19 +00:00
- uses: stefanzweifel/git-auto-commit-action@v4.1.6
2020-02-23 10:42:57 +00:00
with:
commit_message: Apply php-cs-fixer changes
```
2020-01-11 20:32:17 +00:00
## Known Issues
- GitHub currently prohibits Actions like this to push changes from a fork to the upstream repository. See [issue #25](https://github.com/stefanzweifel/git-auto-commit-action/issues/25) for more information.
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.