You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I wanted to merge my fix GH fix, I saw that the Docs CI failed. After looking at the failure, I saw that it was unrelated to my change, but was caused by a recent enum documentation change: https://bugs.python.org/issue40066#msg410711
I reverted the enum change to merge my PR. The enum PR was merged even if the Docs CI failed. Well, the Docs job is not mandatory.
Should we make the Docs CI mandatory on the Python main branch? cc @tiran@zware
Is there a reason to not make the Docs CI mandatory? Was it flaky last months? cc @willingc@JulienPalard
Hi,
When I wanted to merge my fix GH fix, I saw that the Docs CI failed. After looking at the failure, I saw that it was unrelated to my change, but was caused by a recent enum documentation change: https://bugs.python.org/issue40066#msg410711
I reverted the enum change to merge my PR. The enum PR was merged even if the Docs CI failed. Well, the Docs job is not mandatory.
Should we make the Docs CI mandatory on the Python main branch? cc @tiran @zware
Is there a reason to not make the Docs CI mandatory? Was it flaky last months? cc @willingc @JulienPalard
By the way, who has access to the Python branch protection now? I used to ping Brett, but he wrote that he prefers to no longer be responsible for that. https://mail.python.org/archives/list/python-committers@python.org/thread/GB7T23XWLNKR24V5IWBADYSLFK6KWCY6/
Victor