Repository navigation
Decrease bot permission #83
Description
One of the goal for mr meeseeks is to not have write permission to repositories for security reason as most actions are done via the meeseeksmachine user though it currently have write permission via "content".
Contents
Repository contents, commits, branches, downloads, releases, and merges.
But also only to "pull requests"
Pull requests
Pull requests and related comments, assignees, labels, milestones, and merges.
See https://github.com/organizations/MeeseeksBox/settings/apps/meeseeksdev/permissions if you have access.
I'd like to discuss what we can do to disable global write access to content, and which action it can perform that would be affected. For example I don't know if code reformatting on PR requires "content" access or "Pull requests" access.
Activity
blink1073 commentedon Apr 18, 2022
As I understand it, the "Pull requests" access allows you to edit metadata about the Pull Request itself (labels, title, comments, etc). We need contents access on the org to "push as maintainer" to the branch, or contents access from the requestor to push directly to their fork.