pagure

#4542 API token creation lacks the option to allow for Pull request creation
Closed: Invalid by pingou. Opened by nhorman.

Closed: Invalid
Reopen Issue

I'm enhancing rpkg to allow for interaction with pagure instances, and in testing against pagure.io, I received an EINVALTOK response to the create PR REST endpoint, which I found odd as my API token had all ACLs selected. When I went to go recreate my token to ensure everything was right, I noticed that the ACL to enable pull request creation wasn't available. It seems that that ACL option needs to be enabled. Could someone take care of that please?

This sounds like an infrastructure issue, pagure itself (the software) supports this :)

Hi Neil,

I suspect that this is about the OSCI instance of Pagure?

@msrb no, its specifically about pagure.io. src.osci.redhat.com has the ACL to allow creation of pull requests already. I'm attaching screenshots of both sites for comparison
Screenshot_from_2019-07-16_07-31-39.pngScreenshot_from_2019-07-16_07-31-52.png

ping, any update here? I really need this to work for the fedpkg/rhpkg feature I'm developing

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

Updates on this can be found here: https://pagure.io/fedora-infrastructure/issue/8013
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.