After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 776691 - Please add information about where to find the pull request closing robot and bug report URLs to pull request closing messages
Please add information about where to find the pull request closing robot and...
Product: sysadmin
Classification: Infrastructure
Component: Git
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Reported: 2017-01-01 20:31 UTC by Till Maas
Modified: 2018-09-21 15:26 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Till Maas 2017-01-01 20:31:32 UTC

is a message the a robot closed my pull request but it does not say where to find the robots source code or where to report bugs. I found

which states that the git repo name corresponds to the Bugzilla product, however I only found the product "sysadmin", but the repo is called "sysadmin-bin":

Also a direct link to the robot python script on

would be nicer so one does not need to search for the python script there.

Additionally it would be great if the message just contained a link to file the bug report in bugzilla, e.g.

in my case.
Comment 1 Olav Vitters 2017-01-03 23:00:11 UTC
A repository isn't the same as a a bugzilla product. There's a doap file which can have one or more bugzilla references. This could be parsed for a helpful URL. ftpadmin (also in sysadmin-bin) already parses these doap files. To retrieve the doap of a specific git module the following can be used: The pinpoint doap file doesn't contain a Bugzilla reference though.
Comment 2 GNOME Infrastructure Team 2018-09-21 15:26:42 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: