#195 The request-branch help does not indicate which ACLs my pagure token should have
Closed: Fixed 5 years ago Opened 6 years ago by bowlofeggs.

The help text on request-branch should indicate which ACLs should be requested on Pagure tokens:

Before requesting a new dist-git repository for a new package, you need to
generate a pagure.io API token at https://pagure.io/settings/token/new, and save it
into your local user configuration located at ~/.config/rpkg/fedpkg.conf. For
example:

    [fedpkg.pagure]
    token = <api_key_here>

After visiting Pagure, I am presented with these optional permissions to grant to the token:

  • Create a new project
  • Fork a project
  • Comment on a ticket
  • Create a new ticket
  • Modify an existing project

According to the fedrepo-req readme file "Create a new ticket against this project" is the required permission.


Metadata Update from @cqi:
- Issue set to the milestone: NEXT

6 years ago

Metadata Update from @cqi:
- Issue assigned to cqi

6 years ago

Commit 7affb33 fixes this issue

Metadata Update from @cqi:
- Issue set to the milestone: 1.33 (was: NEXT)

5 years ago

Login to comment on this ticket.

Metadata