Detector / Fixer chaining workaround #676

Activity

1. github-actions commented on Mar 12, 2026

   

   github-actionsBot

   on Mar 12, 2026 – with GitHub Actions

   Contributor

   More actions

   3 related issues

   • Split pr check fix into pr ci detective and pr ci fixer #121 — it tracks splitting detection and fix execution into separate workflows, which aligns with this issue’s dispatch-based workaround to decouple runs.
   • [product-manager-impersonator] Expose no-op workflow_call outputs for scheduled workflows #663 — it documents detector/fixer chaining constraints in scheduled workflows, which can help when designing reliable cross-workflow chaining behavior.
   • Remove Fixer workflows #436 — it discusses triggering follow-up fix flows from detection flows, which is closely adjacent to this issue’s proposed audit/fix separation.

   ---

   What is this? | From workflow: Trigger Duplicate Issue Detector

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
2. github-actions commented on Mar 12, 2026

   

   github-actionsBot

   on Mar 12, 2026 – with GitHub Actions

   Contributor

   More actions

   tl;dr: #676 is valid and actionable now — current docs/examples encourage same-run detector→fixer chaining, but compiled workflows still use a fixed artifact name (activation), so a temporary split-workflow workaround is the safest recommendation until upstream github/gh-aw#20685 ships.

   Recommendation

   Recommend a temporary docs-first workaround: run detector/audit and fixer in separate workflows, and trigger the fixer via workflow_dispatch (new workflow run = separate artifact namespace). Keep current same-run chaining docs, but add a clear “known limitation / temporary workaround” notice linked to upstream github/gh-aw#20657 + github/gh-aw#20685.

   Findings

   Code and docs evidence

   • Chaining is explicitly promoted in docs:
     • docs/workflows/detector-fixer-chaining.md:3
     • docs/workflows/detector-fixer-chaining.md:49-68
     • docs/workflows/gh-agent-workflows.md:72
     • docs/upgrading.md:11,30-33
   • Trigger generation also appends same-run chaining:
     • scripts/dogfood.sh:138-147
     • Generated example: .github/workflows/trigger-docs-patrol.yml:21-27
   • Compiled workflows use static activation artifact naming (upload + download):
     • .github/workflows/gh-aw-text-auditor.lock.yml:675-683 and 1178-1182
     • .github/workflows/gh-aw-create-pr-from-issue.lock.yml:440-448 and 1010-1014
   • Upstream status:
     • Bug report: github/gh-aw#20657 (409 conflict for artifact name)
     • WIP fix: github/gh-aw#20685 (artifact manager for workflow_call contexts)

   Related repo history:

   • #476 / PR #504 introduced and documented single-run output-based chaining.
   • PR #589 expanded issue→PR auto-chaining in generated triggers.

   Verification

   Commands and output

   $ grep -nE "Upload activation artifact|name: activation|Download activation artifact" .github/workflows/gh-aw-text-auditor.lock.yml
   675:      - name: Upload activation artifact
   679:          name: activation
   1178:      - name: Download activation artifact
   1181:          name: activation
   
   $ grep -nE "Upload activation artifact|name: activation|Download activation artifact" .github/workflows/gh-aw-create-pr-from-issue.lock.yml
   440:      - name: Upload activation artifact
   444:          name: activation
   1010:      - name: Download activation artifact
   1013:          name: activation
   
   $ grep -nE "single workflow run|created_issue_number|create-pr-from-issue|if: needs\.run\.outputs\.created_issue_number" docs/workflows/detector-fixer-chaining.md docs/upgrading.md scripts/dogfood.sh
   ... (matches at lines cited in Findings)

   Detailed Action Plan

   Implementation plan (repo-local)

   1. Add a Known Limitation section to docs/workflows/detector-fixer-chaining.md near the top (after intro), stating same-run chaining can hit artifact-name conflicts in current upstream compiler/runtime.
   2. Add a temporary workaround example in the same doc: detector workflow emits issue; separate fixer workflow with workflow_dispatch takes issue_number input and runs gh-aw-create-pr-from-issue.
   3. Add short caveat/cross-link in:
      • docs/workflows/gh-agent-workflows.md:72
      • docs/upgrading.md:11 (also rename “single action run” → “single workflow run”).
   4. Keep current examples for future state, but label them as dependent on upstream fix availability/version.
   5. Once github/gh-aw#20685 is merged + released, upgrade compiler version in this repo, recompile lock workflows, then remove/relax the temporary caveat.

   Related Items

   Issues, PRs, and files

   Type	Link	Relevance
   Issue	#676	Current triage request
   Upstream Issue	github/gh-aw#20657	Root bug report: artifact name conflict (activation)
   Upstream PR	github/gh-aw#20685	WIP upstream artifact-manager fix
   Issue	#476	Earlier output/chaining investigation
   PR	#504	Added/advertised detector/fixer single-run chaining
   PR	#589	Expanded generated issue→PR chaining
   File	docs/workflows/detector-fixer-chaining.md	Primary user guidance to update
   File	docs/upgrading.md	Feature messaging and terminology to adjust
   File	docs/workflows/gh-agent-workflows.md	Catalog page that links chaining guidance
   File	scripts/dogfood.sh	Generates same-run remediation chain in triggers

   ---

   What is this? | From workflow: Trigger Issue Triage

   Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
3. strawgate

   assigned

   Copilot

   and

   strawgate

   on Mar 12, 2026