Hi devs, GitHub provides a mechanism which is able to require branches to be up to date before merged[1](point 6). I can see several advantages enabling it. Thus propose our project to turn on this switch. Below are my concerns. Looking forward to your insights.
1. Avoid CI failures in pr which fixed by another commit. We now merge a pull request even if CI fails but the failures knowns as flaky tests. We doesn't resolve this by turn on the switch but it helps to find any other potential valid failures. 2. Avoid CI failures in master after pull request merged. Actually, CI tests the branch that pull request bind exactly. Even if it gave green it is still possible a systematic failure introduced because conflicts with another new commit merged in master but not merged in this branch. For the downside, it might require contributors rebase his pull requests some times before getting merged. But it should not inflict too much works. Best, tison. [1] https://help.github.com/en/articles/enabling-required-status-checks
