1. 10 Sep, 2014 1 commit
  2. 04 Apr, 2013 2 commits
  3. 10 Oct, 2012 1 commit
    • Chuck Atkins's avatar
      Make all hook references relative to thier location · 646b891d
      Chuck Atkins authored
      Some hooks were getting referenced directly via $GIT_DIR/hooks while at
      other times getting referenced relative via ${BASH_SOURCE%/*}.  By making
      all references relative then these hooks can reside in a different folder
      and still be daisy-chained by other hooks.
      646b891d
  4. 29 Feb, 2012 1 commit
    • Brad King's avatar
      Set GIT_DIR if not already set · 5ebbe2da
      Brad King authored
      Although it seems reasonable to expect GIT_DIR to be set when
      hooks are invoked, the "git help hooks" documentation does not
      guarantee it.  On msysGit 1.7.8 (and perhaps others) "git gui"
      runs prepare-commit-msg without setting GIT_DIR.  Set GIT_DIR
      at the beginning of each commit hook if it is not already set.
      5ebbe2da
  5. 06 Feb, 2012 1 commit
  6. 06 Oct, 2011 1 commit
    • Brad King's avatar
      Load local hooks configuration from work tree · 18358af3
      Brad King authored
      Look for a ".hooks-config.bash" file at the top of the work tree.
      Load it in each hook to get per-project configuration.  Currently
      we do not define any config options, but this adds the framework.
      18358af3
  7. 13 Jan, 2011 1 commit
  8. 16 Nov, 2010 1 commit
    • Brad King's avatar
      Chain to script configured by "hooks.chain-<hook>" · dc31be5b
      Brad King authored
      Chain the pre-commit, commit-msg, and prepare-commit-msg hooks to
      locally configured scripts.  Interpret relative paths with respect to
      the working directory where the hooks run (top of work tree).  This
      allows project setup scripts to add project-specific checks for each of
      these hooks.
      dc31be5b