commit | ee269b64a608de770696d23079f46238c2f7ab5a | [log] [tgz] |
---|---|---|
author | Anthony Sottile <asottile@umich.edu> | Fri Mar 06 13:23:31 2020 -0800 |
committer | Anthony Sottile <asottile@umich.edu> | Fri Mar 06 13:23:31 2020 -0800 |
tree | 74186d03409d8bcdfaa92ae468a6cd4f35c61f60 | |
parent | 4fce1afd0c5c66f88bcea0e2d0afc93a14bd799f [diff] |
also include the location of the python in the cache key
a GitHub action to run pre-commit
To use this action, make a file .github/workflows/pre-commit.yml
. Here's a template to get started:
name: pre-commit on: pull_request: push: branches: [master] jobs: pre-commit: runs-on: ubuntu-latest steps: - uses: actions/checkout@v1 - uses: actions/setup-python@v1 - name: set PY run: echo "::set-env name=PY::$((python --version --version && which python) | sha256sum | cut -d' ' -f1)" - uses: actions/cache@v1 with: path: ~/.cache/pre-commit key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }} - uses: pre-commit/action@v1.0.1
This does a few things:
pre-commit
cacheHopefully in the future when actions
matures the yaml can be simplified.
this action also provides an additional behaviour when used in private repositories. when configured with a github token, the action will push back fixes to the pull request branch.
here's an example configuration for that (use the template above except for the pre-commit
action):
- uses: pre-commit/action@v1.0.1 with: token: ${{ secrets.GITHUB_TOKEN }}
note that secrets.GITHUB_TOKEN
is automatically provisioned and will not require any special configuration.
while you could technically configure this for a public repository (using a personal access token), I can't think of a way to do this safely without exposing a privileged token to pull requests -- if you have any ideas, please leave an issue!