Hi, Please don't attempt to merge PRs until the GitHub issue described below is solved ;-) Pablo renamed the default "master" branch to "main" (in a live Twitch stream ;-)) but got a GitHub internal error! Maybe it's because the dialog announced that 1.4k+ pull requests and 700+ repositositories will be impacted which is not a common case. Right now, there are "main" and "master" branches. I reported the issue to GitHub Support forum: https://github.community/t/renaming-python-master-branch-to-main-1-4k-prs-70... Victor On Mon, May 3, 2021 at 5:59 PM Pablo Galindo Salgado <pablogsal@gmail.com> wrote:

Hi everyone,

Unfortunately, the CI for master is currently quite unstable and he had some problems that we have been fixing all weekend and today. We are doing our best to stabilize the test suite and making sure that everything is ready to go for the release with no issues, but this will take some time (also bear in mind that today is a bank holiday in the UK, so I am doing my best to get the release ready in a holiday). Given this and the fact that we need to do a branch rename, **we have decided to block the master branch** until we can stabilize the test suite.

In the meantime, if you have some urgent fix or PR that you absolutely need to get merge before feature freeze, you can add me as a reviewer to said PR so we can evaluate the merge.

Thanks for your understanding.

I will update once master is unblocked again.

Regards from cloudy London, Pablo Galindo Salgado

_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/A... Code of Conduct: https://www.python.org/psf/codeofconduct/

-- Night gathers, and now my watch begins. It shall not end until my death.

Hi, Please don't attempt to merge PRs until the GitHub issue described below is solved ;-) Pablo renamed the default "master" branch to "main" (in a live Twitch stream ;-)) but got a GitHub internal error! Maybe it's because the dialog announced that 1.4k+ pull requests and 700+ repositositories will be impacted which is not a common case. Right now, there are "main" and "master" branches. I reported the issue to GitHub Support forum: https://github.community/t/renaming-python-master-branch-to-main-1-4k-prs-70... Victor On Mon, May 3, 2021 at 5:59 PM Pablo Galindo Salgado <pablogsal@gmail.com> wrote:

Hi everyone,

Unfortunately, the CI for master is currently quite unstable and he had some problems that we have been fixing all weekend and today. We are doing our best to stabilize the test suite and making sure that everything is ready to go for the release with no issues, but this will take some time (also bear in mind that today is a bank holiday in the UK, so I am doing my best to get the release ready in a holiday). Given this and the fact that we need to do a branch rename, **we have decided to block the master branch** until we can stabilize the test suite.

In the meantime, if you have some urgent fix or PR that you absolutely need to get merge before feature freeze, you can add me as a reviewer to said PR so we can evaluate the merge.

Thanks for your understanding.

I will update once master is unblocked again.

Regards from cloudy London, Pablo Galindo Salgado

_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/A... Code of Conduct: https://www.python.org/psf/codeofconduct/

-- Night gathers, and now my watch begins. It shall not end until my death.