Just wanted to point out a few new features from GitHub that may (or may not!)
be useful for Python’s use of Github:

* Required status checks no longer requiring a branch to be up to date.

  Previously turning on required status checks meant that to merge a branch
  into a protected branch, you the target branch could not contain any commits
  that  didn’t exist in the PR. This effectively made the feature useless for
  OSS projects, but it could be useful now. Of course this would also mean that
  all changes need to happen via PR instead of directly pushing to a protected
  branch, so it may not still be useful for Python.

* Squash Merges, Regular Merges, or Both.

  Previously the GitHub "Merge" button would always do a regular, no fast
  forward merge which kept all of the commits that the original author made
  intact. However GitHub now allows a repository to decide what kind of merges
  it allows, either that or sqaush merges (or it can allow both). If it allows
  both then the person doing the merge gets to pick what kind of merge I think.

  A Squash merge will be most similar to how patches used to land on Python
  and would prevent history from getting clogged up with needless commits from
  people who don't edit history to keep their PRs clean, however it might lose
  history from people who do.