Is your feature request related to a problem? Please describe.
When people want to use git hooks to check something on the project, send notifications, or any kind of action, they have to know a bit of bash scripting or any other console language like python.

Describe the solution you'd like
It could be interesting to accept script proposals, like "I have a project X and would like to have a pre-commit script that lints every file commited with their respective linter". Then someone with enough knowledge (and time) could write that script and add it to the repo. Proposals could be Github issues for example, but it should be nice to add something like "if you don't find the script you want, you can ask for it in a new issue" in the Readme.

Is your feature request related to a problem? Please describe.
We are always on the lookout for new Git hooks to add to this awesome list! It can be any kind of Git hook as long as it is ethical and appropriate. In order to qualify as being "awesome", it should be useful in some way and it should follow the Contribution Guidelines.

Describe the solution you'd like
You can contribute a new Git hook that is either:

1. original and written by you
2. a script you found somewhere, but it must be okay to copy and you must cite the source

Once you are ready to contribute a Git hook, feel free to create a new pull request! Also feel free to post any questions below. Happy coding!

hi
Thanks for those nice scripts.

does the post-checkout code also fire when renaming a branch?

Is your feature request related to a problem? Please describe.
The enforce-insert-issue-number script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example.

This project uses the BATS testing framework.

Description of Bug
If the user tries to checkout the branch they are currently on, the "new-branch-alert" hook is activated. It should not be activated in this case.

Steps to Reproduce
Steps to reproduce the behavior:

1. In terminal, type git checkout [current-branch-name]
2. See error

Expected Behavior
The new-branch-alert message should not appear in this scenario.

Screenshots

Description of Bug
After running the verify-name-and-email unit tests, the local git config is unconditionally updated with a hardcoded user.name and user.email.

Steps to Reproduce
Steps to reproduce the behavior:

1. Run bats tests/verify-name-and-email-test.bats
2. Run git config --local user.name; git config --local user.email
3. Observe name/email in output

Expected behavior
Any existing local config for user.name and user.email should be preserved. If there isn't a local configuration for those fields, they should remain unset.

$ git config --local --remove-section user

# note: no output (fields are unset)
$ git config --local user.name
$ git config --local user.email

$ bats tests/verify-name-and-email-test.bats
 ✓ incorrect name throws error
 ✓ incorrect email throws error

2 tests, 0 failures

# note new values
$ git config --local user.name
Lauren Stephenson
$ git config --local user.email
[email protected]

Is your feature request related to a problem? Please describe.
The readme has a list of scripts separated by git hook, but I can't see what language the script depends on without opening it.

Describe the solution you'd like
It could be nice to identify the language of the script (maybe a small icon next to the title), so people can see the requirements. For example, if we have a server that does not have perl installed, maybe we can't use a perl script.

Hello! Great project, thanks for it. I use lefthook for management git hooks, it is very fast and really nice hook manager. Can I add to this?

https://github.com/igorkamyshev/kamyshev.me.src/

Description of Bug
A clear and concise description of what the bug is.
Hi when creating a new branch if it's start with a number (like new default Gitlab recommended branch naming convention) {issuenumber}-{title} ex : 15-styleborder the new-branch-alert.hook will not fire

Steps to Reproduce
Steps to reproduce the behavior:

1. Create a branch '15-styleborder the hook will not fire'
2. Now create a branch 'styleborder-15 the hook will fire as expected

Expected behavior
the new-branch-alert.hook 'should fire' whatever naming format used for the new branch

Thanks

Problem

When working with multiple projects, sometimes you want to use a different name or email address for the projects. If you don't use the correct ones, it can cause the commit history on the repository to look different than what was intended.

Solution

Create a sample that, upon enabling, will abort the commit if the user name or email is incorrect.

The "format-code" git hook will fail to commit if one of the added changes is the deletion of a file.

The current work-around is to run the formatting command manually, then add "--no-verify" to the end of the git commit command.

Add tests for the verify-name-and-email script.

Testing framework: https://github.com/sstephenson/bats

The "new-branch-alert" hook is the only current git hook to help solve the problem of checking out a new branch and forgetting to update the submodules to reflect the new branch name. This "new-branch-update-maven-submodules" git hook would automatically update the submodules when a new branch is created, then commit the code and display an informative message in the console.

Command: mvn clean -N versions:update-child-modules -DgenerateBackupPoms=false
Look into how to make it fully automatic rather than making user change the parent version prior to running above command.

Problem

After mvn fmt:format is run, it can potentially modify the code. So it needs to be re-added before committing.

Solution

Add line to end of file: git diff --name-only --cached | xargs -l git add

Also, clarify that the commit format run command will re-add any files that were modified after being staged. However, if a file was not staged before running commit command, it will still not be added after code is reformatted by format command.

Look into ensuring code coverage is equal to or greater than previous release

Possible resource: https://www.atlassian.com/continuous-delivery/continuous-integration/git-hooks

Is your feature request related to a problem? Please describe.
The delete-pyc-files script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example. Here is another example.

This project uses the BATS testing framework.

Is your feature request related to a problem? Please describe.
The prevent-bad-push script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example. Here is another example.

This project uses the BATS testing framework.

Is your feature request related to a problem? Please describe.
The search-term script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example. Here is another example.

This project uses the BATS testing framework.

It would be beneficial to add a new section on the readme containing a list of useful tools that can be used to improve user experience/management of git hooks. The new section could be called "Tools for Working with Git Hooks" or something similar.

Is your feature request related to a problem? Please describe.
The new-branch-alert script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example. Here is another example.

This project uses the BATS testing framework.

Is your feature request related to a problem? Please describe.
The spell-check-md-files script doesn't have any tests yet.

Describe the solution you'd like
Add one or more unit tests. Here is an example.

This project uses the BATS testing framework.

Is your feature request related to a problem? Please describe.
It's very difficult to see the bash icon in dark mode.

Describe the solution you'd like
A different icon that's visible in both themes, or use GitHub's officially supported way of presenting a different image depending on the light/dark mode