René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Should we make the Docs CI mandatory on the Python main branch?","articleBody":"Hi,\r\n\r\nWhen I wanted to merge my [fix GH](https://github.com/python/cpython/pull/30631) 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\r\n\r\nI 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.\r\n\r\nShould we make the Docs CI mandatory on the Python main branch? cc @tiran @zware \r\n\r\nIs there a reason to not make the Docs CI mandatory? Was it flaky last months? cc @willingc @JulienPalard \r\n\r\nBy 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/\r\n\r\nVictor","author":{"url":"https://github.com/vstinner","@type":"Person","name":"vstinner"},"datePublished":"2022-01-17T16:06:10.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/424/core-workflow/issues/424"}