Skip to contentSkip to conversation

push: document --no-verify

PATCH In review Michael S. Tsirkin 2 participants 3 messages Jun 15, 2016 Documentation

lore
Share & tools
lore

Michael S. Tsirkin

author
#0 lore raw

PATCH 1/1 push: document --no-verify

commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added --no-verify flag to git push, but didn't document it. It's a useful flag when using pre-push hooks so add the documentation.

Suggested-by Thomas Rast <[email protected]>
Cc Aaron Schrab <[email protected]>
Signed-off-by Michael S. Tsirkin <[email protected]>
---
 Documentation/git-push.txt | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)
Documentation/git-push.txt +6 -1
index d514813..346b28a 100644
@@ -11,7 +11,7 @@ SYNOPSIS
 [verse]
 'git push' [--all | --mirror | --tags] [--follow-tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
 	   [--repo=<repository>] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream]
-	   [<repository> [<refspec>...]]
+	   [--no-verify]  [<repository> [<refspec>...]]
 
 DESCRIPTION
 -----------

@@ -162,6 +162,11 @@ useful if you write an alias or script around 'git push'.
 	linkgit:git-pull[1] and other commands. For more information,
 	see 'branch.<name>.merge' in linkgit:git-config[1].
 
+-n::
+--no-verify::
+	This option bypasses the pre-commit and commit-msg hooks.
+	See also linkgit:githooks[5].
+
 --[no-]thin::
 	These options are passed to linkgit:git-send-pack[1]. A thin transfer
 	significantly reduces the amount of sent data when the sender and
Signature · 1 line
MST
#1 lore raw
Quoted 8 lines · Michael S. Tsirkin

commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added --no-verify flag to git push, but didn't document it. It's a useful flag when using pre-push hooks so add the documentation.

Suggested-by Thomas Rast <[email protected]>
Cc Aaron Schrab <[email protected]>
Signed-off-by Michael S. Tsirkin <[email protected]>

[...]

Documentation/git-push.txt useful if you write an alias or script around 'git push'. · line 169

Quoted 5 lines
+-n::
+--no-verify::
Documentation/git-push.txt +3 -0
+	This option bypasses the pre-commit and commit-msg hooks.
+	See also linkgit:githooks[5].
+

Umm, half of that is not correct :-)

Push doesn't have the -n short form that git-commit does, and the hook names are wrong.

I also ended up writing a patch myself; sorry for not telling you on IRC:

http://thread.gmane.org/gmane.comp.version-control.git/225141

Signature · 2 lines
Thomas Rast
trast@{inf,student}.ethz.ch
author
#2 lore raw
Quoted 19 lines · Thomas Rast
Quoted 8 lines · Michael S. Tsirkin

commit ec55559f937727bcb0fa8a3dfe6af68c188e968a added --no-verify flag to git push, but didn't document it. It's a useful flag when using pre-push hooks so add the documentation.

Suggested-by Thomas Rast <[email protected]>
Cc Aaron Schrab <[email protected]>
Signed-off-by Michael S. Tsirkin <[email protected]>

[...]

Documentation/git-push.txt useful if you write an alias or script around 'git push'. · line 169

Quoted 5 lines
+-n::
+--no-verify::
Documentation/git-push.txt +3 -0
+	This option bypasses the pre-commit and commit-msg hooks.
+	See also linkgit:githooks[5].
+

Umm, half of that is not correct :-)

Quoted 1 line

Push doesn't have the -n short form that git-commit does,

Hmm true - in fact -n means dry-run.

Quoted 7 lines

and the hook
names are wrong.

I also ended up writing a patch myself; sorry for not telling you on IRC:

http://thread.gmane.org/gmane.comp.version-control.git/225141

Great, thanks.

Quoted 3 lines
Signature · 2 lines
Thomas Rast
trast@{inf,student}.ethz.ch