You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,3 +52,15 @@ We use `pre-commit` to ensure the code style is consistent. To install pre-commi
52
52
Once you have `pre-commit` installed, the code stylers and linters
53
53
defined in the `pre-commit-config.yaml` will run each time you
54
54
commit modified changes to git locally.
55
+
56
+
### Precommit.ci Bot
57
+
58
+
We use the pre-commit CI bot to run linting tests and to auto fix
59
+
pull requests. How it works:
60
+
61
+
- Pre-commit.ci will run the CI checks via a CI run in the PR.
62
+
- After the PR is approved but before it's merged, a maintainer can run the bot to apply linting fixes via a commit to the PR. To run the bot write:
63
+
64
+
`pre-commit.ci autofix` in a comment in the PR. This will trigger another CI run to double check that the linting / code style fixes are as expected. Then you can merge!
65
+
66
+
NOTE: the pre-commit CI bot CI action will allow you to see what checks pass. It will also remind you of the command to autofix the code in the pr.
0 commit comments