Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decrease bot permission #83

Open
Carreau opened this issue Apr 16, 2022 · 1 comment
Open

Decrease bot permission #83

Carreau opened this issue Apr 16, 2022 · 1 comment

Comments

@Carreau
Copy link
Contributor

Carreau commented Apr 16, 2022

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.

@blink1073
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants