https://bugs.kde.org/show_bug.cgi?id=419221
--- Comment #6 from Nate Graham <n...@kde.org> --- Created attachment 129167 --> https://bugs.kde.org/attachment.cgi?id=129167&action=edit Landed on 20.04 branch GitLab tells you which branch it landed on. See the attachment. As for why the bug wasn't automatically closed, it's because for single-commit merge requests, the final commit message is taken from that commit, not the Merge Request description (as Phabricator did) and you only added the BUG keyword into the MR description, not in the commit message of the original commit. The Merge Request description can only be turned into the final commit message when clicking on the Merge button in the web UI if there are more than one commit and you do a squash merge and rewrite the commit message. Yes, this is a bit confusing. I have documented it at https://community.kde.org/Infrastructure/GitLab#Write_a_good_commit_message to the best of my abilities and files a bug on GitLab itself: https://gitlab.com/gitlab-org/gitlab/-/issues/219747 In the meantime, we need to get in the habit of writing the original commit message as if it was going to be added verbatim into the git history (because now with GitLab, sometimes it will be). -- You are receiving this mail because: You are watching all bug changes.
