Repository navigation
Closed as not planned
Closed as not planned
Copy link
Labels
initiativeEpic / initiative tracking issueEpic / initiative tracking issue
Description
Story
As a maintainer of a repo consuming the CI Failure Analyst template,
I want have the ci-failure-analyst caller, template, and docs pin to a SHA that actually exists on main with an accurate annotation,
so that consumers stop inheriting an off-main pin while the longer tag-based migration lands.
Acceptance Criteria
- The
uses:ref in.github/workflows/ci-failure-analyst.lock.ymlpinsci-failure-analyst-reusable.ymlto a 40-hex SHA that is reachable frommain, with a trailing annotation that accurately names the ref it points to (not a misleading# mainon an off-main SHA). - The identical
uses:ref intemplates/ci-failure-analyst.ymlis updated to the same on-main SHA + accurate annotation. - The
uses:reference shown indocs/aw/ci-failure-analyst.mdis updated to match the new pin so the docs and the workflows agree. - The SHA chosen is verified present on
main(e.g.git merge-base --is-ancestor <sha> origin/main), not on an unmerged branch. - No other workflow's pins are changed; the diff is limited to the three ci-failure-analyst surfaces.
Tasks / Subtasks
- Resolve the current HEAD-of-main commit SHA for ci-failure-analyst-reusable.yml and confirm it is an ancestor of origin/main. (AC: test issue from agent #1, Optimize review: small-PR and incremental fast paths #4)
- Run
git rev-parse origin/main(or pick the merge commit of feat: implement issue #317 — [Fleet Monitor] petry-projects/.github-private — ci-failure-analyst.lock.yml #520/chore(deps): bump the actions group across 1 directory with 8 updates #640 that landed the reusable) and verify withgit merge-base --is-ancestor <sha> origin/main. - SHAs for pinning must be looked up via git/GitHub, never guessed (CLAUDE.md).
- Run
- Replace the off-main pin in the lock caller with the verified on-main SHA and an accurate annotation. (AC: test issue from agent #1, feat: add Copilot engine support via REVIEW_ENGINE toggle #5)
- Edit
.github/workflows/ci-failure-analyst.lock.ymlline 33.
- Edit
- Apply the same repin to the deployable template. (AC: Go-live improvements for PR review agent #2, feat: add Copilot engine support via REVIEW_ENGINE toggle #5)
- Edit
templates/ci-failure-analyst.ymlline 44 (theuses:underjobs.analyze).
- Edit
- Update the docs reference block to match. (AC: Add @claude delegation, auto-merge, and rebase handling #3)
- Edit
docs/aw/ci-failure-analyst.mdline 25.
- Edit
- Run shellcheck/lint and confirm the edited YAML still parses and nothing else regressed. (AC: feat: add Copilot engine support via REVIEW_ENGINE toggle #5)
-
shellcheck scripts/*.shis unaffected; sanity-check the two edited workflow YAMLs parse.
-
Dev Notes
- INTERIM by design: this story removes the actively-broken off-main pin quickly. Story id 5 ([Phase 2]) supersedes it by repinning these same three surfaces to the
@ci-failure-analyst/stablechannel tag once that tag exists. Keep this change minimal so the later tag repin is a clean diff. - The annotation must not lie. Today the pin reads
<sha> # mainbut the SHA is NOT on main — the whole point of the bug. Use an annotation that is verifiable (short SHA or the PR/commit that merged it), or drop the# maincomment if it cannot be made accurate. - All three surfaces carry the SAME
uses:value today; they must stay in lockstep. The lock file is hand-maintained — there is no generator/sync script that would overwrite it (verified: no lock-sync script under scripts/). - Testing standard: this repo gates workflow YAML via the structure tests under
tests/dev-lead/integration/andshellcheck scripts/*.sh(CLAUDE.md). No new test is required for a pin swap, but do not break existing ones. - Do NOT introduce a tag pin here — tags do not exist yet and the
release-channel-tagsruleset does not yet coverci-failure-analyst/**. Tag adoption is Phase 2.
Project Structure Notes
Touches only existing files; no new paths. Caller stub, deployable template, and doc are the three canonical ci-failure-analyst surfaces.
References
- .github/workflows/ci-failure-analyst.lock.yml#L33
- templates/ci-failure-analyst.yml#L44
- docs/aw/ci-failure-analyst.md#L25
- .github/workflows/ci-failure-analyst-reusable.yml
- CLAUDE.md (SHAs looked up via API, never guessed)
Likely target surface
.github/workflows/ci-failure-analyst.lock.ymltemplates/ci-failure-analyst.ymldocs/aw/ci-failure-analyst.md
Story prepared by the BMAD Scrum Master (Bob) for epic #684. Status: ready-for-dev.
Metadata
Metadata
Assignees
Labels
initiativeEpic / initiative tracking issueEpic / initiative tracking issue
Activity
don-petry commentedon Jul 14, 2026
Superseded / not needed. This stopgap was to get consumers off the broken off-main SHA while the tag migration landed. That migration has since landed —
ci-failure-analyst/stablenow exists (#1159/#1165) and the template already pins to it. The correct fix for the one remaining off-main caller (.github/workflows/ci-failure-analyst.lock.yml:33, still@0ef7b61… # main) is to pin it straight to@ci-failure-analyst/stable— folded into #689 — not to an interim on-main SHA. Closing as superseded. — Claude Code