Automatically commit and push changed files back to GitHub with this GitHub Action for the 80% use case.
Go to file
2019-09-22 14:52:33 +02:00
actions.yml Use GITHUB_ACTOR instead of args 2019-09-20 20:34:57 +02:00
CHANGELOG.md Tag v2.1.0 2019-09-20 21:20:34 +02:00
Dockerfile Update Icon 2019-06-10 14:37:29 +02:00
entrypoint.sh Use GITHUB_ACTOR instead of args 2019-09-20 20:34:57 +02:00
LICENSE Create LICENSE 2019-06-10 15:00:49 +02:00
README.md Update README 2019-09-22 14:52:33 +02: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 Committer is "GitHub Actions actions@github.com" and the Author of the Commit is "Your GitHub Username github_username@users.noreply.github.com.

If no changes are available, the Actions does nothing.

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

Usage

Add the following step at the end of your job.

- uses: stefanzweifel/git-auto-commit-action@v2.1.0
  with:
    commit_message: Apply automatic changes
    branch: ${{ github.head_ref }}
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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

Inputs

The following inputs are required

  • commit_message: The commit message used when changes are available
  • branch: Branch name where changes should be pushed to

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.

name: php-cs-fixer

on:
  pull_request:
    paths:
    - '*.php'

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.1.0
      with:
        commit_message: Apply php-cs-fixer changes
        branch: ${{ github.head_ref }}
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

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.