git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] push: document --no-verify

From
MTMichael S. Tsirkin <mst@redhat.com>
Date
May 22, 2013, 10:43 UTC
Message-ID
<20130522104356.GA5472@redhat.com>

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 <trast@inf.ethz.ch>
Cc: Aaron Schrab <aaron@schrab.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 Documentation/git-push.txt | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index d514813..346b28a 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -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
-- 
MST
Next: Thomas Rast
Message 1 of 3 in “push: document --no-verify”
  1. push: document --no-verifyMichael S. Tsirkin, May 22, 2013
  2. Thomas RastMay 22, 2013
  3. Michael S. TsirkinMay 22, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.