Automatically commit and push changed files back to GitHub with this GitHub Action for the 80% use case.
Go to file
Stefan Zweifel d69e5f0850 WIP
2020-02-23 10:16:26 +01:00
.github Update Workflow 2019-12-12 21:10:29 +01:00
.eslintrc.json Add package.json and other JavaScript related files 2020-02-11 20:50:22 +01:00
.gitignore Add package.json and other JavaScript related files 2020-02-11 20:50:22 +01:00
action.yml Simplify index.js 2020-02-11 21:04:18 +01:00
CHANGELOG.md Tag v3.0.0 2020-02-06 21:15:35 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2019-10-03 20:19:57 +02:00
entrypoint.sh WIP 2020-02-23 10:16:26 +01:00
index.js WIP 2020-02-23 10:16:26 +01:00
LICENSE Create LICENSE 2019-06-10 15:00:49 +02:00
package-lock.json Add @actions/exec 2020-02-11 21:00:40 +01:00
package.json Add @actions/exec 2020-02-11 21:00:40 +01:00
README.md fix typo in README.md 2020-02-08 12:28:25 +08:00

git-auto-commit-action

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".

If no changes are detected, the Action does nothing.

This Action has been inspired and adapted from the auto-commit-Action of the Canadian Digital Service and this commit-Action by Eric Johnson.

This Action currently can't be used in conjunction with pull requests of forks. See issue #25 for more information.

Usage

Note: This Action requires that you use action/checkout@v2 or above to checkout your repository.

Add the following step at the end of your job.

- uses: stefanzweifel/git-auto-commit-action@v3.0.0
  with:
    commit_message: Apply automatic changes

    # Optional name of the branch the commit should be pushed to
    # Required if Action is used in Workflow listening to the `pull_request` event
    branch: ${{ github.head_ref }}

    # Optional git params
    commit_options: '--no-verify --signoff'

    # Optional glob pattern of files which should be added to the commit
    file_pattern: src/\*.js

    # Optional local file path to the repository
    repository: .

    # Optional commit user and author settings
    commit_user_name: My GitHub Actions Bot
    commit_user_email: my-github-actions-bot@example.org
    commit_author: Author <actions@gitub.com>

The Action will only commit files back, if changes are available. The resulting commit will not trigger another GitHub Actions Workflow run!

It is recommended to use this Action in Workflows which listen to the pull_request event. If you want to use the Action on other events, you have to hardcode the value for branch as github.head_ref is only available in Pull Requests.

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.

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

    - uses: stefanzweifel/git-auto-commit-action@v3.0.0
      with:
        commit_message: Apply php-cs-fixer changes
        branch: ${{ github.head_ref }}
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

    - uses: stefanzweifel/git-auto-commit-action@v3.0.0
      with:
        commit_message: Apply php-cs-fixer changes

Inputs

Checkout action.yml for a full list of supported inputs.

Troubleshooting

  • 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. (Updating the token value with a Personal Access Token should fix your issues)

Known Issues

  • GitHub currently prohibits Actions like this to push changes from a fork to the upstream repository. See issue #25 for more information.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

License

This project is licensed under the MIT License - see the LICENSE file for details.