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

Replace Delete Merged Branch app with native GitHub feature #42

Closed
danielbachhuber opened this issue Nov 23, 2022 · 3 comments
Closed
Assignees

Comments

@danielbachhuber
Copy link
Member

GitHub will delete merged branches for us, so we don't need Delete Merged Branch app anymore.

Done is:

  • Delete Merged Branch app is replaced with the native GitHub feature on every repository.
@danielbachhuber
Copy link
Member Author

@schlessera I enabled 'Automatically delete merged branches' on all of the repositories and removed the Delete Merged Branch app.

Also, I removed the Settings app because it comes with this issue:

WARNING: Note that this app inherently escalates anyone with push permissions to the admin role, since they can push config settings to the master branch, which will be synced. In a future, we may add restrictions to allow changes to the config file to be merged only by specific people/teams, or those with admin access (via a combination of protected branches, required statuses, and branch restrictions). Until then, use caution when merging PRs and adding collaborators.

Until restrictions are added in this app, one way to preserve admin/push permissions is to utilize the GitHub CodeOwners feature to set one or more administrative users as the code owner of the .github/settings.yml file, and turn on "require code owner review" for the master branch. This does have the side effect of requiring code owner review for the entire branch, but helps preserve permission levels.

We were only using it to sync labels

@schlessera
Copy link
Member

Great, removal of the Settings app makes sense as well, as we decided to rethink labels anyway.

@danielbachhuber
Copy link
Member Author

as we decided to rethink labels anyway.

@schlessera Created an issue for that too #54

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

No branches or pull requests

2 participants