[repo] protected branch: remove requirement for PRs to be up to date with master

[blueyed]

@paltman
It makes sense when transitioning to a new build system, but by now I think you should rather update all older PRs, and then we can disable it - in the end it only requires to update all PRs once one has been merged.

[blueyed]

CircleCI does not test the merge commit after all currently.. :/

See https://discuss.circleci.com/t/show-test-results-for-prospective-merge-of-a-github-pr/1662/

[blueyed]

@paltman
While at it, please also remove the removed py35djmaster and py36djmaster jobs from being successful.

[paltman]

I believe this is complete.

[paltman]

Well, at least the py35djmaster and py36djmaster are no longer checked. Was there something else?

[blueyed]

I think the "Update branch" button indicates that the branch has to be up-to-date with master still?

Otherwise there is #422 (in a separate issue).

[paltman]

#422 is merged. Can this be closed?

[blueyed]

The main issue is still there:

I think the "Update branch" button indicates that the branch has to be up-to-date with master still?

[paltman]

Are you talking about the "update branch" on Github PRs? I'm confused.

[paltman]

Oh, I see now. I mostly override it if there are no conflicts. Why does it really matter one way or another?

[paltman]

Also, in my experience, CircleCI is, in fact, rerunning after I update the branch from master.