| |
| Posted by Zachary Lund in reply to Andrei Alexandrescu | PermalinkReply |
|
Zachary Lund
Posted in reply to Andrei Alexandrescu
| >Some of you may have noticed that Brad Roberts has configured bugzilla so it gets notifications from github when fixes get pushed. This makes things easier and more consistent.
>Just be sure and use "Issue nnnn" somewhere in the commit message when checking in a fix for bugzilla nnnn.
>Use "Issue nnnn,mmmm,oooo" etc., when fixing multiple issues with one commit.
According to the Github website:
-------------------------------------------------------------------------
This service hook posts comments on Bugzilla bugs when commit messages
reference a bug by id number.
Bugs are recognised by the following formats, which are case-insensitive:
- Ticket 123
- Bug 123
- Tracker item 123
Multiple bugs can also be specified by separating them with a comma,
apersand, plus or "and":
- Bug 123, 124 and 125
If the "Integration Branch" option is filled in, only commits to that branch
will result in bugs being modified. This is useful for disabling premature bug
closing/comments when working on feature branches.
If "Integration Branch" is not set, commits to all branches will be
processed. If you only want to update Bugzilla when you push to your "main"
branch: you probably want to set this to "master".
If the central repository option is enabled and there is a "fix",
"close", or "address" before the bug then that bug is closed.
If a commit has already been mentioned in the bug comments when pushed
by another user then a comment isn't made, unless the central repository
option is enabled. In this case only the first line of the commit message
is included in the bug comment.
This hook requires Bugzilla version >= 3.4 to function correctly
and >= 4.0 to be able to close bugs.
-----------------------------------------------------------------------------
|