#7478 New zodbot command: .modularity <issue_number>
Closed: Fixed 5 years ago by kevin. Opened 5 years ago by asamalik.

  • Describe what you need us to do:

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].

So, for example, a .modularity 120 would make zodbod say:

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

  • When do you need this? (YYYY/MM/DD)

No date.

  • When is this no longer needed or useful? (YYYY/MM/DD)

When the Modularity WG stops existing.

  • If we cannot complete your request, what is the impact?

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)

5 years ago

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

:ophiuchus:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

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. ;(

Login to comment on this ticket.

Metadata