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

Set 'master' branch to 'protected', once created #1

Open
vcgeers opened this issue Dec 7, 2017 · 3 comments
Open

Set 'master' branch to 'protected', once created #1

vcgeers opened this issue Dec 7, 2017 · 3 comments
Assignees

Comments

@vcgeers
Copy link
Member

vcgeers commented Dec 7, 2017

Following discussion at MIRI Software telecon of Dec 7th, we'd recommend setting the 'master' branch to be a 'protected' branch, to disable force-pushes and the associated risk of losing work.

This can be done by going to "Settings" > "Branches" > "Protected Branches" and then add "master" to it. This can only be done once this repo has been initialised and a 'master' branch has been created.

@vcgeers vcgeers self-assigned this Dec 7, 2017
@vcgeers
Copy link
Member Author

vcgeers commented Feb 1, 2018

Hi Jane,

Now that this repo has been populated, would you like us to mark the master branch as protected, to avoid any risk of force pushes?

@vcgeers
Copy link
Member Author

vcgeers commented Feb 9, 2021

Noticed this was still open. @jemorrison, would you prefer the master branch to be set to protected?
If not, then we'll leave it as is, and close the issue.

@jemorrison
Copy link
Collaborator

I am not sure I really care either way. You can go ahead and mark the master branch protected. If I encounter any problems with it mark protected I will let you know

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