Skip to content

Switch to workflow dispatch for gh-aw - #93

Merged
strawgate merged 12 commits into
mainfrom
workflow-dispatch
Feb 18, 2026
Merged

strawgate merged 12 commits into
mainfrom
workflow-dispatch

Conversation

@strawgate

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Requesting changes based on the inline comment.


What is this? | From workflow: PR Review Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #93

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Requesting changes; please address the permission scope issue noted inline.


What is this? | From workflow: PR Review Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #93

workflow_dispatch:

jobs:
run:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

[MEDIUM] Missing caller permissions for reusable workflow

Reusable workflows cannot elevate the GITHUB_TOKEN beyond what the caller grants. With no permissions: block here, the called workflow’s issues: write (and other write scopes) will be denied, so create_issue/add_comment safe-outputs can fail. Please add explicit permissions in this trigger (and the other trigger-* workflows) matching each called workflow’s needs (e.g., issues: write, pull-requests: write, contents: write where required).

@github-actions

Copy link
Copy Markdown
Contributor

CI failed because make compile left the repo dirty (compiled gh-aw lock files were out of date), so the “Ensure lock files are up to date” step failed. I regenerated the compiled workflows with gh-aw v0.45.1 (same output as the CI compile step) and committed the updated lock files plus the regenerated maintenance workflow.

Snippet showing the regenerated workflow header:

# .github/workflows/agentics-maintenance.yml:1-19
#
# This file was automatically generated by pkg/workflow/maintenance_workflow.go (v0.45.1). DO NOT EDIT.
#
# To regenerate this workflow, run:
#   gh aw compile

Tests run:

  • make lint
  • ./scripts/dogfood.sh && bin/gh-aw compile --action-tag v0.45.1

What is this? | From workflow: Pr Checks Fix

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

Warning

⚠️ Firewall blocked 4 domains

The following domains were blocked by the firewall during workflow execution:

  • dl.google.com
  • golang.org
  • proxy.golang.org
  • telemetry.business.githubcopilot.com

@github-actions

Copy link
Copy Markdown
Contributor

CI failed because make compile leaves the working tree dirty; the generated lock files in .github/workflows/*.lock.yml (and agentics-maintenance.yml) are out of date for the current gh-agent-workflows sources.

Evidence: .github/workflows/ci.yml checks for a dirty tree after compile (L37-L44):

37:       - name: Compile workflows
38:         run: make compile
39:       - name: Ensure lock files are up to date
40:         run: |
41:           if [ -n "$(git status --porcelain)" ]; then
42:             echo "Working tree dirty after make compile."
43:             git status --porcelain
44:             exit 1

Recommended fix (regenerate and commit lock files):

./scripts/dogfood.sh
bin/gh-aw compile --action-tag v0.45.1   # matches Makefile GH_AW_VERSION

Then commit the updated .github/workflows/*.lock.yml plus .github/workflows/agentics-maintenance.yml.

Files updated by compile
  • .github/workflows/agentics-maintenance.yml
  • .github/workflows/agent-efficiency.lock.yml
  • .github/workflows/breaking-change-detect.lock.yml
  • .github/workflows/bug-hunter.lock.yml
  • .github/workflows/code-simplifier.lock.yml
  • .github/workflows/docs-drift.lock.yml
  • .github/workflows/downstream-health.lock.yml
  • .github/workflows/gh-aw-upgrade-check.lock.yml
  • .github/workflows/issue-triage.lock.yml
  • .github/workflows/mention-in-issue.lock.yml
  • .github/workflows/mention-in-pr.lock.yml
  • .github/workflows/pr-checks-fix.lock.yml
  • .github/workflows/pr-review.lock.yml
  • .github/workflows/semantic-function-clustering.lock.yml
  • .github/workflows/small-problem-fixer.lock.yml
  • .github/workflows/stale-issues.lock.yml
  • .github/workflows/test-improvement.lock.yml

Tests run: ./scripts/dogfood.sh && bin/gh-aw compile --action-tag v0.45.1.

Note: I did not push because this workflow run disallows editing .github/workflows/; please regenerate and commit the lock files from your branch.


What is this? | From workflow: Pr Checks Fix

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

Warning

⚠️ Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

  • proxy.golang.org
  • telemetry.business.githubcopilot.com

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Requesting changes based on the inline comment.


What is this? | From workflow: PR Review Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #93

steps:
- name: Setup Scripts
uses: ./actions/setup
uses: github/gh-aw/actions/setup@v0.43.23-224-g8a42439f9-dirty

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

[HIGH] Non-existent action ref will break the workflow

github/gh-aw/actions/setup@v0.43.23-224-g8a42439f9-dirty looks like a local/dirty build tag and is not a published ref in github/gh-aw, so this step will fail to resolve at runtime. Please pin to a published tag/sha (for example the version in .github/aw/actions-lock.json) so the maintenance workflow can actually run.

@strawgate
strawgate merged commit 7ec3c2c into main Feb 18, 2026
4 of 5 checks passed
@strawgate
strawgate deleted the workflow-dispatch branch February 18, 2026 05:47
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.

1 participant