Protected branches and required status checks

Re:Protected branches and required status checks by leehro on Thursday September 03, 2015 @01:17PM (#10166182)

This is great, particularly the "Update Branch" feature. Prior to that, the only way to update a branch (or a fork for that matter) was to use an external client to merge in upstream changes and push back to GitHub.

I worked on a project with several non-developer users updating content. The web interface works well for simple HTML/CSS changes, but if we developers moved or renamed a file, their forks would immediately be useless. This feature should make that a non-issue.

[ Parent | on HN ]

Re:Protected branches and required status checks by brandonwamboldt on Thursday September 03, 2015 @01:20PM (#10166208)

I kind of wish you could merge or rebase as part of the "Update Branch" feature. I don't allow merging master into the feature branches for any project I manage, I insist that developers rebase their branches before they get merged instead.

[ Parent | on HN ]