Skip to content

docs/contributing.md describes .github/workflows/test-flask.yaml, which was removed in 97b300c #3766

Description

@melbinjp

docs/contributing.md (line 28) tells contributors:

  • A CI workflow (.github/workflows/test-flask.yaml) runs Flask's test suite to catch downstream regressions.

That workflow no longer exists. It was removed in 97b300c ("add zizmor to scan workflows", 2026-04-03); the same commit modified lock.yaml, pre-commit.yaml, publish.yaml and tests.yaml and added zizmor.yaml, but test-flask.yaml was deleted rather than updated, and the commit message doesn't mention it. The current workflow set is lock, nightly, pre-commit, publish, tests, zizmor, and none of them run Flask's suite as far as I can see.

So the docs describe a downstream safety net that isn't running. Two different fixes depending on intent, which is why I'm asking rather than sending a patch:

  • If dropping it was deliberate: happy to open a PR removing that bullet from docs/contributing.md.
  • If it was collateral in the zizmor pass, then the Flask downstream regression check has been off since April and the docs are the only thing that noticed.

Found this with a tool I'm building that verifies documentation claims against the repository and its git history; the "documented file was deleted and never restored" check is what flagged it. Happy to send either patch, or neither if you'd rather handle it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsUpdates to documentation, readme, docstrings, typosrejected AIContribution rejected because of its untrustworthy AI origintestsClick's own test suite and CI workflows

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions