This article was published on September 3, 2015

Github introduces Protected Branches to help keep projects on the right track


Github introduces Protected Branches to help keep projects on the right track

As Github projects start splintering into side projects and teams grow, the chances of things getting a bit muddled scale. Now, administrators can protect their branches, and keep a project silo’d until they’re ready for changes.

Protected Branches, which Github is rolling out over the next few weeks, allows repository administrators the ability to disable force pushes for branches.

abe590ca-5031-11e5-9bee-dacc64b99db2

Those protected branches can also have required status checks to the master branch, and administrators have the ability to disable merges until their branches are up-to-date with the master.

The <3 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol' founder Boris, and some questionable AI art. It's free, every week, in your inbox. Sign up now!

It’ll keep projects a bit locked down, but will ultimately help developers keep things on the right track. If you’ve ever pushed an update to the wrong branch, this will help prevent it from happening again.

Protected branches and required status checks [Github]

Get the TNW newsletter

Get the most important tech news in your inbox each week.

Also tagged with


Published
Back to top