Repository navigation
ci: trim comments in project-status.yml (#1967) - #2059
Merged
Merged
Conversation
Drop the comment text that duplicates conventions/process.rst (the built-in board workflows, the PROJECT_TOKEN scopes and skip notice) and tighten the security and concurrency notes. The reconcile-race note moves beside the concurrency block it explains. Every why, the GitHub docs citation and the #1967 ref stay; no YAML changes.
Owner
Author
|
GOOD TO GO at
|
Owner
Author
|
Ready to merge at |
Contributor
|
Coverage: 91.52% (unit tier, Python 3.15,
Per-file detail: the |
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
make pylint,make mypy,make isort)make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
ci— changes to CI configuration files and scriptsDescription of your pull request and other information
Step 5 of #1967 (comment trim, job by job), for
project-status.yml. Comments only; the file stays semantically identical, checked withyaml.safe_loadagainstmain.process.rst's "Milestones and the Project Board" section already says. That covers the built-in board workflows, the test that holds the table to the file, and thePROJECT_TOKENsetup; the header now points there instead.concurrency:key it explains.workflow_dispatchtrust argument, the cron backstop and its timing,permissions: {},timeout-minutes, and the GitHub concurrency docs link.No test pins this file's comment text. Every workflow-reading test in
tests/projectpasses (775 passed), and pinned actionlint 1.7.12 exits 0 with Lint's ignore list.