pull_request jobs fail on permissions
See original GitHub issueThe packit jobs triggered on PR https://github.com/oamg/convert2rhel/pull/82 say:
Submit of the build failed: Only owners and admins may update their projects.
But @SpyTec has another PR, https://github.com/oamg/convert2rhel/pull/78, where the jobs run fine. @SpyTec is an admin of the https://github.com/oamg/convert2rhel/ repo.
The only reason that comes to my mind is that the PR is marked as a draft.
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (12 by maintainers)
Top Results From Across the Web
You need the Git 'Pull Request Contribute' permission to ...
We are getting the below error while submitting the Pull Request. ... According your description, you do not seem have the permissions to...
Read more >Workflow syntax for GitHub Actions
If a job fails, all jobs that need it are skipped unless the jobs use a conditional expression that causes the job to...
Read more >Not able to see such branch permission as
Its just the master branch when getting a Pull Request triggers a build to the Jenkins job via a webhook and Jenkins sends...
Read more >octokit/rest.js
Check if a pull request has been merged; Create a pull request; Create a reply for a review comment; Create a ... Re-run...
Read more >git pull request failed with “Permission denied (publickey)” error
You need to check if your public/private key is: set with the default names id_rsa , id_rsa.pub (instead of id_rsa_github for instance); set...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bocekm I’ll take a look. The problem is that we are trying to update copr project settings (chroots, removal, additional_repos,…) each time to be able to change the settings also after the copr project creation. That can be a problem for the custom project since we don’t permissions to do the updates.
I would like to implement the following fix:
We need to ask for that permission so they can grant it to us. (We can do that manually if you need it ASAP.)
You can also remove the custom project/user from config for now.