You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Right now, the master branch is protected, and requires status checks before code can merge. This causes PRs to have to be based off of the newest commit in master (see bottom of this blog post). This makes it very difficult to merge multiple PRs - as soon as one PR is merged, every other waiting PR must be rebased.
One solution to this would be to have an unprotected develop branch that PRs are merged into. This develop branch could be merged into master and next each weekly release. A second option could be to have a releases branch that is protected and make master unprotected. A third, and simplest, option would be to simply turn off the protected status for master.
The text was updated successfully, but these errors were encountered:
Going to disable the mandatory status checks feature. This will let us merge PRs that aren't based on the very latest commit, which will be nicer to everyone. We still expect and require all tests to pass, but this won't be done through Github's protected branches feature.
Right now, the
master
branch is protected, and requires status checks before code can merge. This causes PRs to have to be based off of the newest commit in master (see bottom of this blog post). This makes it very difficult to merge multiple PRs - as soon as one PR is merged, every other waiting PR must be rebased.One solution to this would be to have an unprotected
develop
branch that PRs are merged into. Thisdevelop
branch could be merged intomaster
andnext
each weekly release. A second option could be to have areleases
branch that is protected and makemaster
unprotected. A third, and simplest, option would be to simply turn off the protected status formaster
.The text was updated successfully, but these errors were encountered: