Skip to content

Commit

Permalink
ci: Describe running locally
Browse files Browse the repository at this point in the history
Doing so gives the developer feedback early on, before the changes hit
the GitHub CI infrastructure.

This would be a good candidate for using a Git pre-hook. Unfortunately,
gitlint is a bit tricky to be used in a pre-push hook:
jorisroovers/gitlint#55
  • Loading branch information
rettichschnidi committed Apr 26, 2021
1 parent 6ea3d16 commit a5aa7a7
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,8 @@ To check if your code matches the expected style, the following commands are hel
If existing code gets reformatted, this must be done in a separate commit. Its commit id has to be added to the file
`.git-blame-ignore-revs` and committed in yet another commit!.

### Running CI tests locally
To avoid unneeded load on the GitHub infrastructure, please consider running `tools/ci/run_ci.sh --all` before pushing.

## Examples

Expand Down

0 comments on commit a5aa7a7

Please sign in to comment.