Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: pre-commit/action
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.0.0
Choose a base ref
...
head repository: pre-commit/action
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.0.1
Choose a head ref

There isn’t anything to compare.

v2.0.0 and v2.0.1 are entirely different commit histories.

Showing with 3 additions and 3 deletions.
  1. +3 −3 README.md
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -25,7 +25,7 @@ jobs:
steps:
- uses: actions/checkout@v2
- uses: actions/setup-python@v2
- uses: pre-commit/action@v2.0.0
- uses: pre-commit/action@v2.0.1
```
This does a few things:
@@ -43,7 +43,7 @@ Here's a sample step configuration that only runs the `flake8` hook against all
the files (use the template above except for the `pre-commit` action):

```yaml
- uses: pre-commit/action@v2.0.0
- uses: pre-commit/action@v2.0.1
with:
extra_args: flake8 --all-files
```
@@ -68,7 +68,7 @@ pushing
next is passing the token to the pre-commit action

```yaml
- uses: pre-commit/action@v2.0.0
- uses: pre-commit/action@v2.0.1
with:
token: ${{ secrets.GITHUB_TOKEN }}
```