Protecting the master branch #230
gillisandrew
started this conversation in
General
Replies: 1 comment
-
Did a force push to fix the commit history as some of the commits didn't properly follow conventional commits. The other part was just a new action though that should have been done as a pr though given its nature I need to do a few to make sure its working fine as you can't replicate that part properly. Luckily the plugin I've added seems to mostly check that but we need to make 100% sure that's enforced otherwise the features/fixes wont show in the automatic changelogs. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey guys, if were gonna working on this together I think it would be a good idea to stop pushing directly to master (especially force pushes 👀). Repo owner should be able to disable merging without pull request and protect specific branches through repo settings.
Handle updates through pull-requests so contributors can rebase off master and have release-ready code without any broken builds and whatnot.
Beta Was this translation helpful? Give feedback.
All reactions