You can import tasks from your private or public pagure
instance using the
pagure service name.
Here’s an example of a Pagure target:
[my_issue_tracker] service = pagure pagure.tag = releng pagure.base_url = https://pagure.io
The above example is the minimum required to import issues from Pagure. You can also feel free to use any of the configuration options described in Common Service Configuration Options or described in Service Features below.
Note that either
pagure.repo is required.
pagure.tagoffers a flexible way to import issues from many pagure repos. It will include issues from every repo on the pagure instance that is tagged with the specified tag. It is similar in usage to a github “organization”. In the example above, the entry will pull issues from all “releng” pagure repos.
pagure.repooffers a simple way to import issues from a single pagure repo.
Note – no authentication tokens are needed to pull issues from pagure.
Include and Exclude Certain Repositories¶
If you happen to be working with a large number of projects, you
may want to pull issues from only a subset of your repositories. To
do that, you can use the
For example, if you would like to only pull-in issues from
project_fox repositories, you could add
this line to your service configuration:
pagure.tag = fedora-infra pagure.include_repos = project_foo,project_fox
Alternatively, if you have a particularly noisy repository, you can
instead choose to import all issues excepting it using the
pagure.exclude_repos configuration option.
In this example,
noisy_repository is the repository you would
not like issues created for:
pagure.tag = fedora-infra pagure.exclude_repos = noisy_repository
Provided UDA Fields¶
||Created||Date & Time|