fatiando / community

Community resources, guidelines, meeting notes, authorship policy, maintenance, etc.
Other
8 stars 4 forks source link

Make sure "main" branches are protected #57

Closed leouieda closed 2 years ago

leouieda commented 2 years ago

Description:

As a general safety measure, it would be good the main branches of all repositories were protected from force pushes or pushes of any kind really. This way changes have to go through PRs and it's harder to accidentally push to main instead.

Most repos should already have something like this in place but it would be good to double check and make sure it's standard in all our repos.

Apply to:

Further instructions:

We want your help!

We know that maintenance tasks are very demanding, so we don't expect a single person to tackle this issue by themselves. Any help is very welcomed, so please comment below that you want to take care of the changes on any repository and we will assign it to you.

santisoler commented 2 years ago

Done for Harmonica! Thanks for reminding this

By the way, this is what I did for Harmonica. It can serve as a guide for the other repos:

Screenshot 2022-06-22 at 14-21-59 Branch protection rule · fatiando_harmonica

leouieda commented 2 years ago

Thanks for sharing @santisoler! Updated Boule to match.

leouieda commented 2 years ago

Done for all except community which needs to be available for pushes to main by HackMD for the meeting notes archive.