diff options
author | Sean Whitton <spwhitton@spwhitton.name> | 2019-07-19 17:11:22 +0100 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2019-07-20 17:12:05 +0100 |
commit | 45c18da882a7bb95c35973223a01deca171bfb69 (patch) | |
tree | 0ef56be5feaf4f1b1d5e67e0f5885b49fbcdb571 /git-debpush.1.pod | |
parent | c01951dd94161b9e9c2b602b1e308ee4354c9520 (diff) |
git-debpush: Support forcing individual checks
While using git-debpush interactively, if the user sees that checks
have failed which they know to be safe to override, they typically
just use --force or -f.
However, it is useful for scripts to be able to skip single checks,
and if the user knows that a check will fail in advance of running
git-debpush, it is convenient to be able to specify that but still see
whether other checks fail, where those failures were unexpected. This
can avoid the user having to run git-debpush more than once.
The list of any checks which failed but were overridden is not stored
in the generated tag. git-debpush's checks are for the convenience of
the local user only, and the list of failed but overridden checks is
not considered to be metadata for the upload. Not recording failed
but overridden checks in the git tag keeps git-debpush's checking
independent of its wrapping of git-tag and git-push, which makes
git-debpush simpler and easier to understand. The complexity is on
the server side, in tag2upload.
git-debpush(1): We want the list of checks that can be overridden to
be at the bottom of the list of options because most users will not
need to look at it. We also want the description of --force|-f to be
adjacent to the description of --force=<check>. So move the
description of --force|-f to the end of the list of options.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Closes: #932459
Diffstat (limited to 'git-debpush.1.pod')
-rw-r--r-- | git-debpush.1.pod | 38 |
1 files changed, 34 insertions, 4 deletions
diff --git a/git-debpush.1.pod b/git-debpush.1.pod index 242bf67..429148d 100644 --- a/git-debpush.1.pod +++ b/git-debpush.1.pod @@ -146,10 +146,6 @@ upload your package. Just tag, don't push. -=item B<--force>|B<-f> - -Ignore the results of all checks designed to prevent broken uploads. - =item B<-u> I<keyid> Passed on to git-tag(1). @@ -182,6 +178,40 @@ git would use if you typed "git push BRANCH". What distribution name to embed in the signed tag. Defaults to "debian". +=item B<--force>|B<-f> + +Ignore the results of all checks designed to prevent broken uploads. + +=item B<--force>=I<check>[,I<check>] ... + +Override individual checks designed to prevent broken uploads. May be +specified more than once. Valid values for I<check> are: + +=over 4 + +=item B<suite> + +Permit uploading to a different suite than the target of the most +recent upload made with B<git-debpush> (e.g. when uploading to +Debian unstable after uploading to Debian experimental). + +=item B<upstream-nonancestor> + +Ignore the fact that the upstream tag is not an ancestor of the branch +to be tagged (skipping this check is implied by B<--quilt=baredebian>). + +=item B<unreleased> + +Permit upload to a suite called UNRELEASED. + +=item B<dgit-view> + +Ignore apparently pushing the dgit view of a package (as produced by +B<dgit clone>) to the maintainer branch, where the dgit view and the +maintainer view of the package are not identical. + +=back + =back =head1 SEE ALSO |