https://bugs.kde.org/show_bug.cgi?id=404486
--- Comment #5 from Michael Pyne <mp...@kde.org> --- (In reply to jm.ouwerkerk from comment #4) > I am getting a bit confused about how to track issues here. To me it looks > like we have 3 separate places: > > - bugs.kde.org > - phabricator.kde.org (the kdesrc-build workboard) > - invent.kde.org (the kdesrc-build Gitlab repo/project) > > How are these systems related? Am I still supposed to file bugs on > bugs.kde.org at all, anymore? For kdesrc-build, prefer https://invent.kde.org/ for now. b.k.o will remain and if the gitlab experiment doesn't work out then we'll fall back to b.k.o. I can close down the phab board (or just point it to https://invent.kde.org/). > Also looking at the git remotes, I don't see invent.kde.org there at all so > I also don't see how I am supposed to tag my commit message properly for > Gitlab. You don't have to do anything special to write your commit message for invent.kde.org in most situations, except to say something like "Fixes #4" (where '4' is the issue number that is impacted on the Gitlab instance). If/when the Git commit fixing the bug gets pulled into the gitlab-hosted repository, gitlab will close the matching issue itself. For an example please see https://invent.kde.org/kde/kdesrc-build/commit/0ceb50e9fefbc43c037e7303fa66b0e793987b3c You don't actually need to add gitlab as a remote to develop against it, the gitlab-hosted repo syncs back to anongit like normal. It can be more convenient to do so, however. The gitlab instance should be able to point out which commands to run if you want to add gitlab as a remote to submit a Merge Request, or you can always just add the diff to the issue. And if it's all too annoying, feel free to continue to work here or in phab. -- You are receiving this mail because: You are watching all bug changes.
