Skip to content

[Docs] pre-commit setup and use #1107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hugsy merged 4 commits into from
May 21, 2024
Merged

[Docs] pre-commit setup and use #1107

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dfda496
added paragraph explaining how to use pre-commit
hugsy May 19, 2024
fa05c18
md lint
hugsy May 19, 2024
bca8a3c
[ci] pinning actions version in validate.yml
hugsy May 19, 2024
5a3fb23
Apply suggestions from code review
hugsy May 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Apply suggestions from code review 
Co-authored-by: Grazfather <[email protected]>
  • Loading branch information
@hugsy @Grazfather
hugsy and Grazfather authored May 21, 2024
commit 5a3fb236873f9be1657bc1f8ef9e87a50ecb4e1b
4 changes: 2 additions & 2 deletions docs/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,13 +179,13 @@ pre-commit install
```

By default, `pre-commit` will use git hook to run the validation checks after each commit but you
can modify this behavior as wanted or even run it manually
can modify this behavior as desired or even run it manually

```console
pre-commit run --all-files
```

By default, `pre-commit` will report and attempt to fix the code to match what is being currently
By default, `pre-commit` will report and attempt to fix the code to match what the coding style
defined with GEF.


Expand Down