Skip to contentSkip to conversation

githooks documentation: post-checkout hook is also called after clone

PATCH Superseded Jens Lehmann 2 participants 2 messages Jun 15, 2016 Documentation

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 githooks documentation: post-checkout hook is also called after clone

The documentation of the post-checkout hook just talks about git-checkout. But recently git-clone was changed to call it too, so we have to document that in githooks.txt.

---
 Documentation/githooks.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
Documentation/githooks.txt +3 -0
index 1fd512b..76deefc 100644
@@ -151,6 +151,9 @@ indicating whether the checkout was a branch checkout (changing branches,
 flag=1) or a file checkout (retrieving a file from the index, flag=0).
 This hook cannot affect the outcome of 'git-checkout'.
 
+It is also run after 'git-clone'. The first parameter given to the hook is
+the null-ref, the second the ref of the new HEAD and the flag is always 1.
+
 This hook can be used to perform repository validity checks, auto-display
 differences from the previous HEAD if different, or set working dir metadata
 properties.
Signature · 1 line
1.6.2.1.275.ga797b
#1 lore raw
Quoted 17 lines · Jens Lehmann

The documentation of the post-checkout hook just talks about git-checkout. But recently git-clone was changed to call it too, so we have to document that in githooks.txt.

---
 Documentation/githooks.txt |    3 +++

 1 files changed, 3 insertions(+), 0 deletions(-)
Documentation/githooks.txt +0 -0
index 1fd512b..76deefc 100644
@@ -151,6 +151,9 @@ indicating whether the checkout was a branch checkout (changing branches,

 flag=1) or a file checkout (retrieving a file from the index, flag=0). This hook cannot affect the outcome of 'git-checkout'.

Documentation/githooks.txt indicating whether the checkout was a branch checkout (changing branches, · line 156

Quoted 3 lines
Documentation/githooks.txt +3 -0
+It is also run after 'git-clone'. The first parameter given to the hook is
+the null-ref, the second the ref of the new HEAD and the flag is always 1.
+

I don't think that's true if you clone with the --no-checkout (-n) option though.

Quoted 10 lines

 This hook can be used to perform repository validity checks, auto-display differences from the previous HEAD if different, or set working dir metadata properties.
--
1.6.2.1.275.ga797b
--
To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html