From: Thomas Rast Date: Thu, 23 May 2013 13:34:11 GMT Subject: [PATCH v2] Document push --no-verify Message-ID: In-Reply-To: <87vc6arcf4.fsf@linux-k42r.v.cablecom.net> ec55559 (push: Add support for pre-push hooks, 2013-01-13) forgot to add a note to git-push(1) about the new --no-verify option. Signed-off-by: Thomas Rast --- Junio replied privately that it should also mention the --verify possibility. So why not. But this needs to be fixed across the board eventually; 0f1930c (parse-options: allow positivation of options starting, with no-, 2012-02-25) did not update any docs, so none of the other --no- options mention their positive forms. 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..df5be26 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=] [--repo=] [-f | --force] [--prune] [-v | --verbose] [-u | --set-upstream] - [ [...]] + [--no-verify] [ [...]] DESCRIPTION ----------- @@ -195,6 +195,11 @@ useful if you write an alias or script around 'git push'. be pushed. If on-demand was not able to push all necessary revisions it will also be aborted and exit with non-zero status. +--[no-]verify:: + Toggle the pre-push hook (see linkgit:githooks[5]). The + default is \--verify, giving the hook a chance to prevent the + push. With \--no-verify, the hook is bypassed completely. + include::urls-remotes.txt[] -- 1.8.3.rc3.486.gfe16094