"This branch is out-of-date with the base branch" message under PRs

[hishamco]

Today I noticed that the PRs show the following message This branch is out-of-date with the base branch is this something because of the latest patch release or is there something else happening?!!

/cc @MikeAlhayek @Piedone @sebastienros

[MikeAlhayek]

I think @sebastienros changed the repo settings. I am guessing he enabled "Requires branches to be up to date before merging" settings yesterday.

[Piedone]

Yep, that's it. I didn't change it. It's useful though (and as a core contributor you can bypass it too).

[MikeAlhayek]

@sebastienros this option is pretty annoying :). Can we disable it?

It would be nice to have an optional button that would allow us to rebase a PR from UI. But it is annoying that you can't merge a PR without having to rebase even when there is no conflicts. Like if you want to merge PR's back to back. Currently, if you have 2 PRs that you want to merge, you have to merge the first one, rebase the second, then merge the second.

[Piedone]

You can bypass it if you deem the merge safe:

[MikeAlhayek]

@Piedone you must have more access than I do on the project. I Can't by pass it. also it seems that I am only able to update my own branches not others.

[Piedone]

Ah, I see, Hmm, this is dumb like this.

I just learned that there is an "Always suggest updating pull request branches" config that displays this button even without branch protection. So, I enabled that and disabled this from the branch protection rule.

So now you have this:

I think we have the crisis averted, but @sebastienros feel free to reopen and argue, but it seems this just annoys those people who do the most work.