Package: dgit Version: 0.11 Severity: minor Is it necessary for dgit build to check the work tree is clean of uncommitted changes before allowing a build to run?
I don't think it is, because the man page says that I can build by hand using anything I want that generates the right source package. So having all changes committed cannot be an important invariant, since I can easily build with something that doesn't enforce it, and then dgit push. My personal preferred workflow is to make changes, build them, test them, and only once I am satisfied, commit them. This is particularly the case when using UNRELEASED in the changelog, since if if commit a s/UNRELEASED/unstable/ before I actually make the release, I may forget that I've not released it. -- see shy jo
signature.asc
Description: Digital signature
