• via Digitalmars-d-bugs (27/27) Dec 30 2016 https://issues.dlang.org/show_bug.cgi?id=17044

via Digitalmars-d-bugs <digitalmars-d-bugs puremagic.com> writes:

https://issues.dlang.org/show_bug.cgi?id=17044

          Issue ID: 17044
           Summary: Bugzilla integration fails with reverts and multiple
                    branches
           Product: D
           Version: D2
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: tools
          Assignee: nobody puremagic.com
          Reporter: public dicebot.lv

Now that there are at least two development branches (`master` and `stable`),
simplicity of GitHub bugzilla integration becomes a problem.

Consider https://issues.dlang.org/show_bug.cgi?id=16193 - it got originally
fixed with a commit mentioning "fix Issue 16193". Later it got reverted (with
an auto-generated commit saying "Revert "fix Issue 16193 ...") and matching
issues was reopened.

But when revert commit got merged into another branch, bugzilla integration
hook has detected the very same "fix Issue 16193" substring and closed issue
again as fixed (but it wasn't).

Best solution would be for hook to actually recognize revert commits as having
inverse effect of "fixes" mention but I don't know if it can be configured as
such.

--