Add support for Git Hooks
See original GitHub issueI’d love to see support for the git hooks. Some of these hooks are:
-
pre-commit
-
prepare-commit-msg
-
commit-msg
-
post-commit
-
post-merge
-
pre-push
And others. They can be found via this resource and this resource in a more “plain-english” way.
I’m willing to implement this functionality, however, I’m wondering what the API should look like. Do we want to look for the related files and run them with spawn
? Do we want to make pre-X
and post-X
actions and utilize a plugin-like system and provide this logic as an additional package? What do we think?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
githooks Documentation - Git
Hooks are programs you can place in a hooks directory to trigger actions at certain points in git's execution. Hooks that don't have...
Read more >Git Hooks | Atlassian Git Tutorial
Git Hooks are scripts that run automatically every time a particular event occurs in a Git repository. Learn what they do and how...
Read more >Git hooks: How to automate actions in your Git repo - Red Hat
Git hooks are shell scripts found in the hidden .git/hooks directory of a Git repository. These scripts trigger actions in response to specific ......
Read more >Git Hooks | Learn how to use pre-commit hooks, post-commit ...
An introductory guide and resource for Git hooks. Learn how to use pre-commit hooks, post-commit hooks, post-receive hooks, and more.
Read more >Get Started with Git Hooks - Medium
Implementing Git Hooks · 1. Navigate to the hooks directory · 2. Install your hook · 3. Select a language to write your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sounds like a plan
I’m ok for hooks if they get internals of git like refs. But we need to come up with an API that will much the current architecture of passing stuff to each function.