Merged
Conversation
Bumps the gh-aw compiler from a pinned main commit to the v0.51.0 release. Key improvements: - Workflow outputs from safe-outputs: detectors now expose created_issue_number/url and fixers expose created_pr_number/url as workflow_call outputs, enabling single-run detector→fixer chaining (avoids the github-actions[bot] trigger limitation). - Agent failure issues auto-labeled with agentic-workflows. - Bug fixes: checkout token field, activation job dir creation, emoji ZWJ false positives, MCP gateway validation, safe output schema completeness, activation job permissions, report headers. Adds detector/fixer chaining documentation and example-chained.yml files for bug-hunter and code-duplication-detector pairs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThis PR upgrades the gh-aw action infrastructure from commit 3c15f58f to v0.51.0 across 40+ workflow files and supporting configuration. Changes include introducing a Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/gh-aw-stale-issues-remediator.lock.yml (1)
422-422: Consider fully unifying model source to activation output.You now export model from activation (Line 422), but execution env vars still read
inputs.modelin later jobs. Switching those to the propagated model output would keep a single source of truth and avoid future drift.Proposed follow-up diff
- COPILOT_MODEL: ${{ inputs.model }} + COPILOT_MODEL: ${{ needs.activation.outputs.model }}- COPILOT_MODEL: ${{ inputs.model }} + COPILOT_MODEL: ${{ needs.activation.outputs.model }}- GH_AW_ENGINE_MODEL: "${{ inputs.model }}" + GH_AW_ENGINE_MODEL: "${{ needs.agent.outputs.model }}"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/gh-aw-stale-issues-remediator.lock.yml at line 422, The workflow now sets model from the activation job via "model: ${{ needs.activation.outputs.model }}", but downstream job environment variables and any places reading "inputs.model" still use the original input; update those usages to reference the propagated activation output (e.g., replace occurrences of "inputs.model" with "needs.activation.outputs.model" in the jobs that set execution env vars or read the model) so there's a single source of truth; ensure you update all env and step-level references and any default/fallback logic to use needs.activation.outputs.model consistently alongside the existing model variable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.github/workflows/gh-aw-stale-issues-remediator.lock.yml:
- Line 422: The workflow now sets model from the activation job via "model: ${{
needs.activation.outputs.model }}", but downstream job environment variables and
any places reading "inputs.model" still use the original input; update those
usages to reference the propagated activation output (e.g., replace occurrences
of "inputs.model" with "needs.activation.outputs.model" in the jobs that set
execution env vars or read the model) so there's a single source of truth;
ensure you update all env and step-level references and any default/fallback
logic to use needs.activation.outputs.model consistently alongside the existing
model variable.
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (71)
.github/aw/actions-lock.json.github/workflows/agent-deep-dive.lock.yml.github/workflows/agent-efficiency.lock.yml.github/workflows/agentics-maintenance.yml.github/workflows/downstream-users.lock.yml.github/workflows/gh-aw-agent-suggestions.lock.yml.github/workflows/gh-aw-autonomy-atomicity-analyzer.lock.yml.github/workflows/gh-aw-branch-actions-detective.lock.yml.github/workflows/gh-aw-breaking-change-detect.lock.yml.github/workflows/gh-aw-breaking-change-detector.lock.yml.github/workflows/gh-aw-bug-exterminator.lock.yml.github/workflows/gh-aw-bug-hunter.lock.yml.github/workflows/gh-aw-code-duplication-detector.lock.yml.github/workflows/gh-aw-code-duplication-fixer.lock.yml.github/workflows/gh-aw-code-simplifier.lock.yml.github/workflows/gh-aw-deep-research.lock.yml.github/workflows/gh-aw-dependency-review.lock.yml.github/workflows/gh-aw-docs-drift.lock.yml.github/workflows/gh-aw-docs-patrol.lock.yml.github/workflows/gh-aw-duplicate-issue-detector.lock.yml.github/workflows/gh-aw-estc-actions-resource-not-accessible-detector.lock.yml.github/workflows/gh-aw-estc-docs-patrol-external.lock.yml.github/workflows/gh-aw-estc-docs-pr-review.lock.yml.github/workflows/gh-aw-estc-downstream-health.lock.yml.github/workflows/gh-aw-estc-newbie-contributor-patrol-external.lock.yml.github/workflows/gh-aw-estc-pr-buildkite-detective.lock.yml.github/workflows/gh-aw-flaky-test-investigator.lock.yml.github/workflows/gh-aw-framework-best-practices.lock.yml.github/workflows/gh-aw-information-architecture.lock.yml.github/workflows/gh-aw-issue-fixer.lock.yml.github/workflows/gh-aw-issue-triage.lock.yml.github/workflows/gh-aw-mention-in-issue-no-sandbox.lock.yml.github/workflows/gh-aw-mention-in-issue.lock.yml.github/workflows/gh-aw-mention-in-pr-by-id.lock.yml.github/workflows/gh-aw-mention-in-pr-no-sandbox.lock.yml.github/workflows/gh-aw-mention-in-pr.lock.yml.github/workflows/gh-aw-newbie-contributor-fixer.lock.yml.github/workflows/gh-aw-newbie-contributor-patrol.lock.yml.github/workflows/gh-aw-performance-profiler.lock.yml.github/workflows/gh-aw-plan.lock.yml.github/workflows/gh-aw-pr-actions-detective.lock.yml.github/workflows/gh-aw-pr-actions-fixer.lock.yml.github/workflows/gh-aw-pr-ci-detective.lock.yml.github/workflows/gh-aw-pr-review-addresser.lock.yml.github/workflows/gh-aw-pr-review.lock.yml.github/workflows/gh-aw-product-manager-impersonator.lock.yml.github/workflows/gh-aw-project-summary.lock.yml.github/workflows/gh-aw-refactor-opportunist.lock.yml.github/workflows/gh-aw-release-update.lock.yml.github/workflows/gh-aw-scheduled-audit.lock.yml.github/workflows/gh-aw-scheduled-fix.lock.yml.github/workflows/gh-aw-small-problem-fixer.lock.yml.github/workflows/gh-aw-stale-issues-investigator.lock.yml.github/workflows/gh-aw-stale-issues-remediator.lock.yml.github/workflows/gh-aw-stale-issues.lock.yml.github/workflows/gh-aw-test-coverage-detector.lock.yml.github/workflows/gh-aw-test-improvement.lock.yml.github/workflows/gh-aw-test-improver.lock.yml.github/workflows/gh-aw-text-auditor.lock.yml.github/workflows/gh-aw-text-beautifier.lock.yml.github/workflows/gh-aw-update-pr-body.lock.yml.github/workflows/gh-aw-ux-design-patrol.lock.yml.github/workflows/upgrade-check.lock.yml.github/workflows/workflow-patrol.lock.ymlMakefiledocs/upgrading.mddocs/workflows/detector-fixer-chaining.mddocs/workflows/gh-agent-workflows.mdgh-agent-workflows/bug-hunter/example-chained.ymlgh-agent-workflows/code-duplication-detector/example-chained.ymlmkdocs.yml
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This was referenced Mar 8, 2026
3 tasks
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
1 participant
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.
Summary
GH_AW_VERSIONfrom a pinned main commit tov0.51.0and updates.github/aw/actions-lock.jsonforgithub/gh-aw/actions/setup@v0.51.0..github/workflows/agentics-maintenance.ymlto the same setup action SHA.workflow_calloutputs.Key changes from v0.51.0
New features adopted
created_issue_number/created_issue_url, and fixers exposecreated_pr_number/created_pr_urlasworkflow_calloutputs. This enables chaining detector + fixer in a single run without relying on follow-up events fromgithub-actions[bot].agentic-workflows.Features available but not yet adopted
payloadPathPrefix/payloadSizeThresholdare available when needed.Bug fixes picked up by recompilation
tokenfield corrected (checkout.github-token→checkout.token)/tmp/gh-awdirectory creation made reliablecross-repo/authproperties restoredcontents: readpermission addedh3+Documentation and examples
docs/workflows/detector-fixer-chaining.md— New guide for single-run detector→fixer pipelinesgh-agent-workflows/bug-hunter/example-chained.yml— Chained bug-hunter + bug-exterminator examplegh-agent-workflows/code-duplication-detector/example-chained.yml— Chained code-duplication-detector + fixer exampledocs/workflows/gh-agent-workflows.mdandmkdocs.yml— Added links so chaining guidance appears in docs navigationTest plan
make compilesucceeds with v0.51.0outputs:underworkflow_call