https://bugs.kde.org/show_bug.cgi?id=500476
Bug ID: 500476
Summary: Bug Janitor Suggestion: Add comment if merge request
description is edited with a new "BUG:" keyword
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: c...@horwell.me
Target Milestone: ---
SUMMARY
The bug janitor adds a comment "A possibly relevant merge request was started @
" when a merge request is opened with the "BUG:" keyword on a line. However, I
typically can't remember what is valid syntax for this to work ("BUG 123" or
"BUG: 123"? Does "Bug 123" work too?). In particular, by editing the MR
description, nothing happens.
I struggled to find any documentation or code
(https://invent.kde.org/sysadmin/bugzilla-bot) that directly uses this string,
so I'm not sure where/how it works. I'd guess it's some kind of webhook in
GitLab.
As a suggestion, please could:
* The documentation/wiki describe the optional keywords like "BUG:" or "CCBUG:"
when a creating a merge request that directly fixes a bug. Perhaps include
whether the janitor runs on a timer (e.g. every hour) or only at time of the MR
being opened.
* Add a mechanism/hook into GitLab so:
- When a merge request description is edited, summon bot.
- Bot reads Bugzilla comments. If "A possibly relevant..." comment was
found for bug, skip. Otherwise, add comment.
STEPS TO REPRODUCE
1. Open a merge request that fixes a bug, but don't add "BUG: XXX"
2. Edit the description in the merge request and add "BUG: XXXX" (XXX = bug
report number)
OBSERVED RESULT
Bug janitor doesn't inform the bug report. Developer unsure if janitor will
ever come back.
EXPECTED RESULT
Bug janitor posts "A possibly relevant merge request was started" if the
description is updated with new bug references.
--
You are receiving this mail because:
You are watching all bug changes.
