--- Comment #2 from Max Rees (sroracle) <maxcrees(a)me.com> ---
While Bugzilla is great, this is the problem that inevitably arises as
everyone moves to GitHub / GitLab / SourceHut issues: the actual bug
tracking software ecosystem starts to rot.
I did some investigating based on knowing that both Gentoo and FreeBSD
automatically post relevant commits to Bugzilla.
While Gentoo does not use GitZilla directly, it uses a bespoke git
hook that utilizes pybugz, the library underlying GitZilla. However,
pybugz is seemingly unmaintained as well (last activity February
2017). You can see an example of this hook in action at .
FreeBSD does not use git directly of course - their source of truth is
still svn based. They use a bespoke svn hook that emails Bugzilla
directly. The hook itself looks for lines containing only "PR: XXXX" to
grab the bug ID. Bugzilla then grabs the bug ID from the Subject: if it
starts with "[Bug XXXX]". The corresponding part of BugZilla's source is
 I believe. You can see an example of this hook in action at .
In light of this research it seems that just emailing BugZilla directly
as FreeBSD does would seem to be much easier, but it presents two new
1. It must be determined what the hook should be looking for in
commit messages (ideally this should match what GitLab is looking
2. Our Bugzilla instance currently does not support emails:
Hi. This is the qmail-send program at mail.wilcox-tech.com
I'm afraid I wasn't able to deliver your message to the following
This is a permanent error; I've given up. Sorry it didn't work
Sorry, no mailbox here by that name. (#5.1.1)
Of course, there is also the API that can be used. This is much
better documented than the email interface as far as I can tell and
would allow things such as closing a bug.
You are receiving this mail because:
You are the assignee for the bug.