summaryrefslogtreecommitdiff
path: root/git-debpush.1.pod
Commit message (Collapse)AuthorAge
* git-debpush: Check for a detached head when pushing HEADSean Whitton2019-07-22
| | | | | | | See discussion in #932612. Suggested-by: Ian Jackson <ijackson@chiark.greenend.org.uk> Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush: Check for unstitched git-debrebase branchSean Whitton2019-07-22
| | | | | | Closes: #932612 Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush: Check that patches are (un)applicableSean Whitton2019-07-22
| | | | | | Closes: #932477 Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush: Check upstream source is identical in the upstream tagSean Whitton2019-07-20
| | | | | | Closes: #932476 Signed-off-by: Sean Whitton <spwhitton@spwhitton.name> Acked-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* git-debpush: Support forcing individual checksSean Whitton2019-07-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* git-debpush(1): Correct description of --forceSean Whitton2019-07-20
| | | | | | Checks are still performed, but turned from errors into warnings. Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush(1): Tweak AUTHOR sectionSean Whitton2019-07-07
| | | | Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush: Don't pretend to support --baredebian+tarballSean Whitton2019-07-07
| | | | | | | | | Instead of just deleting the option from the argument parser, accept it, but print a message explicitly stating that the *quilt mode* is not supported by this workflow (i.e. it's not just git-debpush passing the quilt mode on to tag2upload that we don't support). Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush(1): Fix POD formattingSean Whitton2019-07-07
| | | | Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
* git-debpush: Support --upstream=TAG (and document it)Ian Jackson2019-07-07
| | | | Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
* git-debpush(1): new manpageSean Whitton2019-07-07
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>