Repository navigation
ci: post the Lint and GitHub Pages reports to Discussions (#2030) - #2056
Merged
Merged
Conversation
Owner
Author
|
GOOD TO GO at
Being fixed: a counted "three jobs" in a |
- lint.yml: a `discussion` job posts the scheduled and dispatched runs to `lint: weekly lint report`. The tool steps get ids and tee their summary blocks to a file; `Write the run report` and `Upload the run report` close the job, skipping pull requests. Advisory failures report `warning`. - deploy-pages.yml: a `discussion` job posts the gate, build and publish results to `deploy-pages: documentation build report`, as `push` on the `workflow_run` and `scheduled` on the schedule, never on a pull request or a verdict for another commit. No artifact; it checks out the script alone. - Only the posting jobs hold `discussions: write`; the hardening, actionlint and loader pins allow for the new job, steps and `env`. - workflows.rst's CI Reports section documents both. Lint is a required check since #1967: the actionlint comment, its docs paragraph and the required contexts table now say so. tests/project/test_lint_pages_reports_2030.py pins both jobs; actionlint 1.7.12 is clean.
JarryShaw
force-pushed
the
ci/2030-scheduled-and-push-reports-2
branch
from
October 22, 2026 21:17
6db758f to
f99d7e9
Compare
Owner
Author
|
GOOD TO GO at
|
Contributor
|
Coverage: 91.54% (unit tier, Python 3.15,
Per-file detail: the |
Owner
Author
|
Ordering check on |
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
The next part of #2030. Lint's and Pages' runs that have no pull request now post to the
CI reportsDiscussions category.lint.yml: scheduled and dispatched runs post every run tolint: weekly lint report. Pull-request runs never post.warningwhen an advisory tool (bandit, mypy, vermin, pylint) failed, elsesuccess.id:, and its summary block is also teed into the report. Write the run report and Upload the run report close the job and arecontinue-on-error, so the check's result is unchanged.deploy-pages.yml: push and scheduled runs post todeploy-pages: documentation build report. Theif:takes the same shape as Vendor's, so pull requests and verdicts for another commit don't post. The status comes from the gate, build and publish results.discussionjob alone holdsdiscussions: write.create-release.ymlis the release workflow.project-status.ymlis the board sync.cron-head.ymlis a reusable gate.tests/project/test_lint_pages_reports_2030.pyfails onmain's two workflows and passes here. Three existing pins accept the new shape:test_actionlint_in_lint_1967,test_workflow_hardening_1968andtest_workflow_loader_1967_unit. These plus the new file:54 passed. actionlint 1.7.12 exits 0, and the PR merges cleanly with build!: require Python 3.8+ and drop the BPC conversion (#2051) #2053.