https://bugzilla.wikimedia.org/show_bug.cgi?id=53388
--- Comment #1 from [email protected] --- (In reply to comment #0) > There are many times when we want to refer to a bug in a commit message (and > get the autolinking), but the patch may not actually be a fix for that bug. That's just why we set the bug's status to PATCH_TO_REVIEW, and not RESOLVED/FIXED :-) > Example: https://gerrit.wikimedia.org/r/#/c/78028/ which refers to bug 52605, > but isn't a patch for it. That's a patch that's closely related bug 52605. It works aroud the bug. Actually, I think it's good to see the link between the bug and the commit. If I'd came across the bug in code I work on, the bug's bugzilla page now has a link to a working solution for the problem. If you want to evade linking, you can put the bug reference in the commit message's body. So for example a commit message like Store the targets list as a serialized string This commit works around bug 52605. Change-Id: I69d48048fe6c5be570472be28774f2a88dd6c9f8 does not touch big 52605. The guidelines at https://www.mediawiki.org/wiki/Gerrit/Commit_message_guidelines#Subject even call for not using bug references in the subject at all. > Another example: https://gerrit.wikimedia.org/r/#/c/80976/ which refers to > bug > 1659, but in pywikibot's sourceforge tracker. That's a separate problem :-) But is there a way we could possibly decide whether or not “bug 1659” refers to our bug tracker or some other site's bug tracker? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
