fix(ci): fail the aggregate when change detection fails, rerun on PR edits, report the real deploy outcome - #999
Merged
Conversation
…edits, and report the real deploy outcome The required ci aggregate skipped the changes job from needs, so a failed paths-filter run skipped the conditional lanes and their skips read green. PR body edits did not rerun the workflow, leaving the issue-close lint stale relative to the current body. The optional Pages audit summary ran under always() but printed an unconditional deployment-success line, even when deploy-pages failed.
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.
Pull Request
Agent Completion Report
t3code/review-cicd-claims-optimizationt3code-9151eea8(linked worktree of the Boris repository)cc096f9fmain(the integration line declared indocs/STATUS.md).github/workflows/ci.yml.github/workflows/github-pages.ymldocs/changelog.d/999-ci-aggregate-changes-and-pages-summary.mdt3code/*, therevert/997-contract-claims-gatecheckout) and their branches are intact and unmodified.ciaggregate: thechanges(dorny/paths-filter) job is now listed inneedsand its result must besuccess. Previously a failed change-detection job skipped the conditional lanes (standalone_tools_test,testdata_generator_test,job-runner-image), and the aggregate's explicitsuccess || skippedacceptance read those skips as green — a broken filter could hide affected tool lanes from a required check.editedevent added to the pull_request trigger so editing a PR body reruns the workflow and thepr-issue-close lintrevalidates the current body (previously, editing a body to fix or break closing-keyword declarations left the lint result stale). Known trade-off, accepted for this slice: theeditedevent reruns the full workflow rather than only the lint lane.always()-guarded summary step now printssteps.deployment.outcomeinstead of an unconditional "succeeded (deploy-pages completed)" line, so a faileddeploy-pagesstep can no longer produce a success claim in the run summary.999-ci-aggregate-changes-and-pages-summary.mdadded perdocs/changelog.d/README.md.incompleteevidence is written; (2)docs/github-pages.mdlists stale Pages action majors and scopes the "no post-deploy HTTP claim" sentence too broadly. Neither is a green/red CI behavior change.npm --prefix editor/ui run checkcould not run (nonode_modulesin the worktree); the editor lane is untouched by this change.git status --short && git branch --show-currentgit fetch origin && git rev-list --left-right --count HEAD...origin/mainzig build test./scripts/release-gate.shzig fmt --check build.zig build.zig.zon src tools test fixtures./scripts/check-pr-issue-close.sh --selftestactionlint .github/workflows/ci.yml .github/workflows/github-pages.yml .github/workflows/greptile-trex.ymlfind docs/changelog.d -maxdepth 1 -type f -name '[0-9]*-*.md' -print | LC_ALL=C sortgit diff --checkzig build test: pass (on basec0305215before the workflow-only edits)./scripts/release-gate.sh: pass ("RELEASE GATE PASSED", includes zig build, zig build test, dual-RAG determinism, IR goldens, fixture diagnostics, cleanliness checks)zig fmt --check …: pass./scripts/check-pr-issue-close.sh --selftest: pass (61 cases)actionlint …: pass (all three workflows)find docs/changelog.d … | LC_ALL=C sort: fragment sorts in numeric order (995,998,999)git diff --check: pass (no whitespace errors).release-gate/scratch from the release gate lives in the ignored tree).incompleteevidence; refreshdocs/github-pages.mdaction-version list in the same or follow-up slice.