You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The compiler adds repositories: ${{ github.event.repository.name }} which limits the GitHub App token to only the triggering repo. Cross-repo workflows need org-wide access (all repos the app is installed on)
Expected solution
Allow to flag workflows that can use Org level scope
The repositories: ["*"] wildcard is the supported way in gh-aw to grant org-wide GitHub App token access. The auth documentation explicitly covers three scoping modes for the github-app: configuration.
If owner is set and repositories is empty, access will be scoped to all repositories in the provided repository owner's installation.
The repositories: ["*"] syntax in gh-aw frontmatter translates to leaving the repositories input empty on the underlying action (passing just owner), which achieves org-wide scope.
Recommendations
Add repositories: ["*"] under the github-app: block in your workflow's tools.github.github-app or safe-outputs.github-app section.
Make sure to also set owner: ${{ github.repository_owner }} (or your org name) — without owner, the token defaults to the current repo owner but the repositories: ["*"] wildcard still needs the owner context.
Ensure the GitHub App is installed at the organization level (not just on individual repos), otherwise org-wide scoping will fail.
Activity
pelikhan commentedon Mar 5, 2026
/scout research how this can be configured. Specifically by using
repositories: ["*"]. Link to docs.github-actions commentedon Mar 5, 2026
🔍 Scout Research Report
Triggered by
@pelikhanExecutive Summary
The
repositories: ["*"]wildcard is the supported way in gh-aw to grant org-wide GitHub App token access. The auth documentation explicitly covers three scoping modes for thegithub-app:configuration.Click to expand detailed findings
Research Findings
How
repositoriesScoping Works in gh-awFrom the Authorization reference docs, the
github-app:configuration supports three modes:repositoriesfieldrepositories: ["*"]repositories: ["repo1", "repo2"]Configuration Example — Tools Authentication
Configuration Example — Safe Outputs Authentication
How This Maps to
actions/create-github-app-tokenUnder the hood, gh-aw uses
actions/create-github-app-token. From that action's docs:The
repositories: ["*"]syntax in gh-aw frontmatter translates to leaving therepositoriesinput empty on the underlying action (passing justowner), which achieves org-wide scope.Recommendations
repositories: ["*"]under thegithub-app:block in your workflow'stools.github.github-apporsafe-outputs.github-appsection.owner: ${{ github.repository_owner }}(or your org name) — withoutowner, the token defaults to the current repo owner but therepositories: ["*"]wildcard still needs the owner context.Key Sources
Suggested Next Steps
repositories: ["*"]andowner:to thegithub-app:block.gh aw compileto regenerate the.lock.yml.References:
pelikhan commentedon Mar 6, 2026
@jaroslawgajewski does this work for you?
jaroslawgajewski commentedon Mar 6, 2026
Yep
As workaround im using different shared definitions depending on scope
pelikhan commentedon Mar 8, 2026
@copilot add FAQ entry on this question.
Use technical-doc-writer agent.