Could we please get a new modularity command to zodbot that would show some details of modularity issues? It would work very similar to the fesco command, but instead it would show issues from the modularity tracker [1].
modularity
fesco
So, for example, a .modularity 120 would make zodbod say:
.modularity 120
Issue #120: Please document how to test `fedpkg module-build` results — modularity — Pagure.io — https://pagure.io/modularity/issue/120
I wanted to send a PR to the repo [2] I believe have these fedora-specific commands, borrowing the code for the 'fesco' command and altering it, but I couldn't grep fesco in that repo. I believe it has some kind of generic ticket functionality and there is a config hidden somewhere.
[1] https://pagure.io/modularity/issues/ [2] https://github.com/fedora-infra/supybot-fedora
No date.
When the Modularity WG stops existing.
Members of the Modularity WG would feel less cool in their meetings, potentially decreasing their happiness and the ability to make the world a better place.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Done.
[10:11:50] <nirik> .modularity 120 [10:11:53] <zodbot> Issue #120: Please document how to test fedpkg module-build results - modularity - Pagure.io - https://pagure.io/modularity/issue/120
fedpkg module-build
:ophiuchus:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
BTW, supybot writes it's own config, so thats why you couldn't see it... someone just added it in and it wrote it to it's local config file. ;(
Thanks, @kevin!
Login to comment on this ticket.