Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Require status checks and reviews before PRs can be merged #59

Closed
zeke opened this issue Mar 29, 2018 · 12 comments
Closed

Require status checks and reviews before PRs can be merged #59

zeke opened this issue Mar 29, 2018 · 12 comments

Comments

@zeke
Copy link
Contributor

zeke commented Mar 29, 2018

This is a followup to #55

I think we should enforce a review requirement on this repo using protected branches. We could also use GitHub's CODEOWNERS feature to ensure that the right teams and people are able to review pull requests before they ship.

@zeke zeke mentioned this issue Mar 29, 2018
@RichardLitt
Copy link
Contributor

Sounds good to me. Who can set this up?

@zeke
Copy link
Contributor Author

zeke commented Mar 30, 2018

I don't have access to the settings tab on this repo.

@bnb
Copy link

bnb commented Apr 2, 2018

@zeke I've made both you and @RichardLitt a maintainer after discussing briefly with @obensource 👍

@obensource
Copy link
Member

@bnb wahoo! Thanks. @zeke @RichardLitt let your progress be impeded no more. 🙌

@zeke
Copy link
Contributor Author

zeke commented Apr 2, 2018

Thanks! I still don't seem to have access to repo settings though 🤔

@RichardLitt
Copy link
Contributor

Thanks @bnb! Me neither.

@zeke
Copy link
Contributor Author

zeke commented Apr 9, 2018

Good day, @bnb! Can you take another peek at this?

@bnb
Copy link

bnb commented Apr 9, 2018

@zeke ah my bad - didn't know there was different RBAC for team maintainers and repos, though it totally makes sense. Y'all should have admin rights for this repo (+ @obensource).

@obensource
Copy link
Member

Thanks for working that out @bnb 👍

@zeke
Copy link
Contributor Author

zeke commented Apr 9, 2018

I've enabled branch protection for master. Here's the current configuration:

image

@zeke
Copy link
Contributor Author

zeke commented Apr 9, 2018

Going to leave this open so we can discuss it during tomorrow's meeting.

@zeke
Copy link
Contributor Author

zeke commented May 11, 2018

Closing this out. We can revisit when and if we need to change our branch protection setup.

@zeke zeke closed this as completed May 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants