Dominik George <naturesha...@debian.org> writes: > Hi,
>> have you considered dgit? > no, as that's something entirely different. dgit does not > manage source packages in Git, it provides a Git frontend > to source packages not managed in Git. No, this is not really true. There's a lot of misunderstanding about dgit. It does in fact manage source packages in Git. You are thinking of the use of dgit for packages that don't use dgit in their upload flow. In those cases, yes, dgit creates a synthetic Git repository that only includes one commit per upload to Debian. Better than nothing, but not really managing the source package in Git. However, if one uses dgit in one's upload flow, all relevant Git changes are pushed to the dgit Git repository. You can close the dgit repository and get exactly the Git repository that the package maintainer used to develop and upload the package, just as if you were using a Git forge. Obviously, dgit doesn't have the other functions of a Git forge, such as issue tracking, CI, or merge requests. But it does manage source packages in Git. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
