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

Enforce pull requests and approvals for all repository updates #216

Closed
kylebarron opened this issue May 13, 2024 · 4 comments
Closed

Enforce pull requests and approvals for all repository updates #216

kylebarron opened this issue May 13, 2024 · 4 comments

Comments

@kylebarron
Copy link
Collaborator

I was looking through the recent commit history because I noticed that CI was broken (#214 (comment)) and I noticed that there were two recent commits that were pushed directly to the main branch without a pull request.

image

In the spirit of openness, I propose that we require a pull request before pushing to main.

I see that in the repository settings we intend to require a pull request before merging
image

but because the
image
box is not checked, this does not apply to people with commit access.

I propose that we enable this box to force all, even administrators, to have at least one approval on a PR.

@kylebarron kylebarron changed the title Enforce pull requests for all repository updates Enforce pull requests and approvals for all repository updates May 13, 2024
@cholmes
Copy link
Member

cholmes commented May 13, 2024

Thanks for flagging this. I think it's important that every change made to the repo/spec is discussed and approved - it's weird to me to have PR's listed in 'closed' that are merged but not approved. I think we should go further than just requiring this in the future, but should revert these changes and have them go through the process. I'd argue that this process has been a 'community norm', and we shouldn't make an exception for these changes. It should be hard to take them through our process.

@jorisvandenbossche
Copy link
Collaborator

I have ticked the "Do not allow bypassing the above settings" box

@kylebarron
Copy link
Collaborator Author

I have ticked the "Do not allow bypassing the above settings" box

With that, we can probably close this issue? Or should we leave it open for any more visibility?

@cholmes
Copy link
Member

cholmes commented May 13, 2024

+1 to just close the issue.

@cholmes cholmes closed this as completed May 13, 2024
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

3 participants