Learn more about these different git repos.
Other Git URLs
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 <img alt="Screenshot_from_2019-07-16_07-31-39.png" src="/pagure/issue/raw/files/f45a5d0a992e292d94306a10bb0b90158b5a999c3f5b17b32e0d4ad9c7b06ff5-Screenshot_from_2019-07-16_07-31-39.png" /><img alt="Screenshot_from_2019-07-16_07-31-52.png" src="/pagure/issue/raw/files/43b74cc3f211255613529f7ae04e974ee5156b2b7982e4652bc1e9750f9479bb-Screenshot_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
Login to comment on this ticket.