You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gitkraken-client/githooks.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -236,6 +236,13 @@ fi
236
236
### Git hook in action
237
237
<imgsrc='/wp-content/uploads/gkc-hook-in-action.gif'class='img-responsive center img-bordered' />
238
238
239
+
### Environment Variables & Git Hooks
240
+
241
+
GitKraken uses a non-interactive shell to run its git hooks so you may need to edit your rc profile (e.g. .bashrc or .zshenv) to allow your extensions and/or environment variables to run in non-interactive shells.
242
+
243
+
Bash shell sources env variables for both interactive and non-interactive definitions from your <i>.bashrc</i> file. But for ZSH, <i>.zshrc</i> is only sourced for interactive shells. Non-interactive definitions for ZSH should go in <i>.zshenv</i>.
244
+
245
+
239
246
### Bypass git hooks
240
247
241
248
There may be times when you want to skip your Git hooks when making a commit. This can be done on a commit-by-commit basis by selecting the `Commit and skip hooks` option.
0 commit comments