Hi!, .. > Is specifying which behaviour to enforce in gbp.conf even possible? > Doesn't it depend on what the commands the maintainer run? How to > convey the intention for each project? How to make tooling yell at the > maintainer to not do the wrong thing? Does any linter notice this?
The debian/gbp.conf should have everything configured. .. > With the --upstream-vcs-tag style, 'gbp dch -R --commit' ends up adding > all upstream commit messages to debian/changelog though, so I found this > approach difficult to use. Do others see that? I'm using > git-buildpackage version 0.9.25, maybe this is fixed in later versions. To only have debian/ changes in the changelog, use command: gbp dch --release --commit -- debian Unfortunately git-buildpackage documentation isn't explaining everything end-to-end, and it is not recommending optimal defaults out-of-the-box. You might want to read as an example the file https://salsa.debian.org/debian/entr/-/blob/debian/latest/debian/README.source.md where I explain every command end-to-end on how to update that package. It is not a Go package, but all commands in it apply to Go packages as well. How to use git or git-buildpackage is not affected by what programming language the upstream project uses.
