- copy the file
commit-msgto.git/hooks/commit-msg - make sure your delete the sample file
.git/hooks/commit-msg.sample - Make commit msg executable.
chmod +x .git/hooks/commit-msg - Edit
commit-msgto better fit your development branch, commit regex and error message - Profit $$
pgilad
/ Instructions.md
Last active
March 31, 2024 22:30
Git commit-msg hook to validate for jira issue or the word merge
moos
/ npm exposed environment variables
Created
November 2, 2017 21:37
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // per https://docs.npmjs.com/misc/scripts, npm exposes a bunch of variables to | |
| // the environment prefixed with npm_config_*, npm_package_* and npm_lifecycle_*. | |
| // Here's a list of all variables exposed in my setup. | |
| npm_config_access= | |
| npm_config_allow_same_version= | |
| npm_config_also= | |
| npm_config_always_auth= | |
| npm_config_argv='{"remain":[],"cooked":["run","foo"],"original":["run","foo"]}' | |
| npm_config_auth_type=legacy |