Open alexsaezm opened 4 months ago
If I understand correctly, the end goal is probably:
tag
or repo
is required -> either tag
or include_repos
is requiredrepo
as redundantI suspect the reason for this limitation in the first place is limitations in pagure's http api, but there's no reason we couldn't hide that under a more consistent configuration abstraction.
Oddly, if you use the tag function, and the repository doesn't have the issues activated (like it happens on Fedora's instance), bugwarrior fails:
This seems like a bug. Please open a separate issue.
So far, the only way I found to retrieve several repositories from a Pagure instance is by having different sections, for example:
The
pagure.include_repos
behaves differently compared togitlab.include_repos
. In Pagure, it is only available if you use thepagure.tag
option, but in GitLab it's the list of repositories to include.pagure.repo
only accepts one item, and having to include several sections in thetargets
field is a little hard, as we cannot use regexp nor wildcards (as far as I know).Oddly, if you use the tag function, and the repository doesn't have the issues activated (like it happens on Fedora's instance), bugwarrior fails:
Is there a way to create something like this?: