[aw] PR Triage Agent failed

[github-actions]

Workflow Failure

Workflow: PR Triage Agent
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/23260181260

🔒 Lockdown Check Failed: The workflow could not start because its security requirements were not met.

This can happen when:

• Lockdown mode (lockdown: true) is enabled but no custom GitHub token is configured. A fine-grained PAT or custom token is required for lockdown mode.

  To fix, configure one of the following repository secrets:

  • GH_AW_GITHUB_TOKEN (recommended)
  • GH_AW_GITHUB_MCP_SERVER_TOKEN (alternative)
  • A custom github-token in the workflow frontmatter

  gh aw secrets set GH_AW_GITHUB_TOKEN --value "YOUR_FINE_GRAINED_PAT"

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/auth.mdx

• The workflow is running on a public repository but was not compiled with strict mode. Recompile the workflow with --strict to meet the security requirements for public repositories.

  gh aw compile --strict

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/security.mdx

Action Required

Option 1: Debug using any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw/actions/runs/23260181260

Option 2: Assign this issue to Copilot

Assign this issue to Copilot using the agentic-workflows sub-agent to automatically debug and fix the workflow failure.

Option 3: Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

• Start your agent
• Load the agentic-workflows prompt from .github/agents/agentic-workflows.agent.md or https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.md
• Type debug the agentic workflow pr-triage-agent failure in https://github.com/github/gh-aw/actions/runs/23260181260

Tip

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from PR Triage Agent · ◷

• expires on Mar 25, 2026, 6:17 PM UTC

[github-actions]

Agent job 23273346793 failed.

🔒 Lockdown Check Failed: The workflow could not start because its security requirements were not met.

This can happen when:

• Lockdown mode (lockdown: true) is enabled but no custom GitHub token is configured. A fine-grained PAT or custom token is required for lockdown mode.

  To fix, configure one of the following repository secrets:

  • GH_AW_GITHUB_TOKEN (recommended)
  • GH_AW_GITHUB_MCP_SERVER_TOKEN (alternative)
  • A custom github-token in the workflow frontmatter

  gh aw secrets set GH_AW_GITHUB_TOKEN --value "YOUR_FINE_GRAINED_PAT"

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/auth.mdx

• The workflow is running on a public repository but was not compiled with strict mode. Recompile the workflow with --strict to meet the security requirements for public repositories.

  gh aw compile --strict

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/security.mdx

Generated from PR Triage Agent · ◷

[github-actions]

Agent job 23282488515 failed.

🔒 Lockdown Check Failed: The workflow could not start because its security requirements were not met.

This can happen when:

• Lockdown mode (lockdown: true) is enabled but no custom GitHub token is configured. A fine-grained PAT or custom token is required for lockdown mode.

  To fix, configure one of the following repository secrets:

  • GH_AW_GITHUB_TOKEN (recommended)
  • GH_AW_GITHUB_MCP_SERVER_TOKEN (alternative)
  • A custom github-token in the workflow frontmatter

  gh aw secrets set GH_AW_GITHUB_TOKEN --value "YOUR_FINE_GRAINED_PAT"

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/auth.mdx

• The workflow is running on a public repository but was not compiled with strict mode. Recompile the workflow with --strict to meet the security requirements for public repositories.

  gh aw compile --strict

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/security.mdx

Generated from PR Triage Agent · ◷

[github-actions]

Agent job 23294081073 failed.

🔒 Lockdown Check Failed: The workflow could not start because its security requirements were not met.

This can happen when:

• Lockdown mode (lockdown: true) is enabled but no custom GitHub token is configured. A fine-grained PAT or custom token is required for lockdown mode.

  To fix, configure one of the following repository secrets:

  • GH_AW_GITHUB_TOKEN (recommended)
  • GH_AW_GITHUB_MCP_SERVER_TOKEN (alternative)
  • A custom github-token in the workflow frontmatter

  gh aw secrets set GH_AW_GITHUB_TOKEN --value "YOUR_FINE_GRAINED_PAT"

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/auth.mdx

• The workflow is running on a public repository but was not compiled with strict mode. Recompile the workflow with --strict to meet the security requirements for public repositories.

  gh aw compile --strict

  See: https://github.com/github/gh-aw/blob/main/docs/src/content/docs/reference/security.mdx

Generated from PR Triage Agent · ◷

[github-actions]

Agent job 23309979470 failed.

Generated from PR Triage Agent · ◷

[github-actions]

Agent job 23323072869 failed.

Generated from PR Triage Agent · ◷