Hi! So I guess the https://pad.debian.net/p/Role_model_README.source.md represents now the most optimal workflow with the current gbp version.
Some day in the future, it would be cool if the instructions could be reduced to just asking people to run these (plus plain git commands between as needed to modify things): gbp clone vcs-git:j4-dmenu-desktop (with no arguments it would automatically add upstreamvcs if one is found in upstream/metadata, and it would mark the upstreamvcs HEAD as the only tracked branch to keep repo tidy) gbp pull (would pull all branches and tags that are relevant for gbp automatically, and also emit a warning if debian/latest seems to be older than what is in archive) gbp import (automatically fetch upstreamvcs tags it exists, use upstream-vcs-tag if exists, and also run uscan, and execute what is currently called import-orig, and finally refresh patches and add minimal new entry in debian/changelog) gbp build (maintainers would repeat this and do git commits in between until everything is perfect) gbp push (if debian/changelog UNRELEASED, would push things without requiring a tag to exist) gbp dch --release --commit (maintainer would do this one all CI and reviews passed) gbp release (dch + source build + upload, tagging and git push delayed if upload was accepted) _______________________________________________ git-buildpackage mailing list [email protected] http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage
