Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Should we make the Docs CI mandatory on the Python main branch? #424

Copy link
Copy link

Description

@vstinner
Issue body actions

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

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.