-
Notifications
You must be signed in to change notification settings - Fork 7
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
Can we give push access while still restricting who can merge to master? #58
Comments
Relevant issue: ipfs/github-mgmt#30 |
User feedback:
|
|
Things to consider: access to repository secrets. |
Unfortunately,
|
Additional feedback on why fork-based workflow might be suboptimal:
|
Giving more people
push
access togithub-mgmt
repositories would simplify the change proposal process - create a branch ingithub-mgmt
vs create agithub-mgmt
fork.Right now, if you have
push
access togithub-mgmt
, you are allowed to merge PRs ie. introduce changes to GitHub configuration.Would it be possible to give people access to create branches but not allow them to merge PRs?
One idea worth exploring is
Require review from Code Owners
setting on protected branches. While it wouldn't restrict anyone from merging PRs, maybe it would allow us to limit the "mergable" PRs only to those already reviewed by a subset of those withpush
access and above.Since this is quite a sensitive task it'll require extensive testing.
The text was updated successfully, but these errors were encountered: