chiark / gitweb /
git-branchmove: Always pass --no-verify to 'git push'
authorSean Whitton <spwhitton@spwhitton.name>
Fri, 30 Aug 2024 11:16:03 +0000 (12:16 +0100)
committerSean Whitton <spwhitton@spwhitton.name>
Thu, 26 Sep 2024 16:03:41 +0000 (17:03 +0100)
commitbf527e4fdf35dd5f4996b2b925bf183936183b16
tree08876413b557613f4d68423278f676bf40cad7d2
parenteef5d90bf41a7f820d3d02b05ea3c21f9f920e8c
git-branchmove: Always pass --no-verify to 'git push'

We are not doing the kind of push for which git pre-push hooks are written, so
they will often fail.  In particular, 'git branchmove' is primarily intended
for moving WIP branches around, whereas pre-push hooks are usually for the
purpose of preventing accidental pushes of unpolished work to public branches.
With this in mind, I think we should try passing --no-verify unconditionally,
instead of providing an option.

Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
scripts/git-branchmove