Skip to content

fix(#1350 post-merge): B-0157 architecture correction + .yml extension + partial pre-existence (4 substantive findings + 3 merge-ordering false positives)#1357

Merged
AceHack merged 1 commit intomainfrom
backlog/B-0157-followup-yml-extension-and-stale-problem-statement
May 3, 2026
Merged

fix(#1350 post-merge): B-0157 architecture correction + .yml extension + partial pre-existence (4 substantive findings + 3 merge-ordering false positives)#1357
AceHack merged 1 commit intomainfrom
backlog/B-0157-followup-yml-extension-and-stale-problem-statement

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented May 3, 2026

Summary

Substantive post-merge review findings on B-0157 absorbed:

  1. Cross-workflow needs: is invalid (line 67 P2) — GitHub Actions `needs:` works only within single workflow file (`jobs.<job_id>.needs`), NOT across workflow files. Architecture correction: row now specifies three options (Architecture A: reusable workflow via `workflow_call` — recommended; Architecture B: per-workflow detect-job; Architecture C: single consolidated workflow).

  2. `.yaml` → `.yml` extension (lines 41 + 66) — all existing workflows use `.yml`; one-off `.yaml` would create drift. Updated throughout.

  3. Stale problem statement (line 35) — `gate.yml` already skips on docs-only via `path-gate`; `codeql.yml` short-circuits pure docs; `backlog-index-integrity` exists. Row now acknowledges partial pre-existence — generalizes pattern, doesn't introduce from zero.

The remaining 3 threads (lines 8, 25, 62) were merge-ordering false positives — B-0142 wasn't present at PR-eval time but merged later as #1349. Resolved with explanation.

Test plan

  • Architecture section corrected with valid GitHub Actions semantics
  • All .yaml references → .yml
  • Partial-pre-existence acknowledgment added
  • markdownlint passes locally

…n + partial pre-existence acknowledged

Three substantive review findings absorbed:

1. Cross-workflow `needs:` is invalid — `needs:` works only within
   single workflow file. Architecture corrected to specify three
   options (Architecture A: reusable workflow via workflow_call;
   Architecture B: per-workflow detect-job; Architecture C: single
   consolidated workflow). Architecture A recommended (matches
   sibling-repo pattern + preserves separation).

2. .yaml → .yml extension throughout — repo's existing workflows
   consistently use .yml; one-off .yaml suffix would create drift.

3. Problem-statement acknowledged partial pre-existence — gate.yml
   already skips on docs-only via path-gate; codeql.yml
   short-circuits pure docs; backlog-only changes have
   backlog-index-integrity. Row generalizes the partial pattern
   into uniform mechanism, NOT from-zero gating.

The B-0142-stale-cross-references in some threads were
merge-ordering false positives (B-0142 not present at PR-eval time;
merged later as #1349) — handled in resolve-thread comments.
Copilot AI review requested due to automatic review settings May 3, 2026 08:13
@AceHack AceHack enabled auto-merge (squash) May 3, 2026 08:14
@AceHack AceHack merged commit ff956bd into main May 3, 2026
24 checks passed
@AceHack AceHack deleted the backlog/B-0157-followup-yml-extension-and-stale-problem-statement branch May 3, 2026 08:15
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates backlog row B-0157 to correct post-merge review findings about GitHub Actions workflow gating semantics and align documentation with existing CI conventions.

Changes:

  • Replaces invalid cross-workflow needs: framing with a 3-architecture explanation (reusable workflow / per-workflow detect-job / consolidated workflow).
  • Normalizes workflow filename references from .yaml to .yml and adds a “partial pre-existence” note acknowledging existing gating.
  • Clarifies which prior findings were merge-ordering false positives vs. substantive corrections.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants