.BR not
prevent dgit from cleaning your tree, so if the changes in your
working tree are in the form of untracked files, those might still be
-deleted.
+deleted, especially with --clean=git.
If you want to include untracked files in the build, you can
-use --clean=none
+use --clean=none or --clean=dpkg-source[-d]
in addition to --include-dirty.
Note that this
combination can fail if the untracked files are under
fixing up. If you use this option and the metadata did in fact need
fixing up, dgit push will fail.
.TP
-.BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied " | " -- [ quilt= ] baredebian [ +tarball ]
+.BR -- [ quilt= ] gbp " | " -- [ quilt= ] dpm " | " --quilt=unapplied " | " -- [ quilt= ] baredebian [ +git | +tarball ]
Tell dgit that you are using a nearly-dgit-compatible git branch,
aka a
.BR "maintainer view" ,
patches in debian/patches).
.B --quilt=baredebian
+(or its alias
+.BR --quilt=baredebian+git )
specifies that your HEAD contains only a debian/ directory,
with any changes to upstream files represented as
patches in debian/patches.