Skip to content

Commit

Permalink
test: Move git hook scripts to tools/
Browse files Browse the repository at this point in the history
They fit better there, tools/ already has the git-hook-pre-rebase hook,
and this cleans up the last bit in test/ which is not actually related
to running integration tests.
  • Loading branch information
martinpitt committed Jun 23, 2022
1 parent 6a0065d commit 2084e13
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions HACKING.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,13 +104,13 @@ There are also static code and syntax checks which you should run often:
It is highly recommended to set up a git pre-push hook, to avoid pushing PRs
that will fail on trivial errors:

$ ln -s ../../test/git-hook-pre-push .git/hooks/pre-push
$ ln -s ../../tools/git-hook-pre-push .git/hooks/pre-push

This calls `test/static-code` for each commit you're trying to push.

You can also set up a post-commit hook to do the same, after each commit:

$ ln -s ../../test/git-hook-post-commit .git/hooks/post-commit
$ ln -s ../../tools/git-hook-post-commit .git/hooks/post-commit

We also have a hook to ameliorate one of the more annoying drawbacks of using
git submodules:
Expand Down
File renamed without changes.
File renamed without changes.

0 comments on commit 2084e13

Please sign in to comment.