[aw] Workshop Content Auto-Updater failed lockdown check

[github-actions]

Workflow Failure

Workflow: Workshop Content Auto-Updater
Branch: main
Run: https://github.com/Azure/git-ape/actions/runs/28823997280
Pull Request: #118

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

Assign this issue to an agent to debug and fix the issue.

Debug with 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/Azure/git-ape/actions/runs/28823997280

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 skill from .github/skills/agentic-workflows/SKILL.md or https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
• Type debug the agentic workflow git-ape-workshop-content-updater failure in https://github.com/Azure/git-ape/actions/runs/28823997280

Tip

Stop reporting this workflow as a failure

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 Workshop Content Auto-Updater · ◷

• expires on Jul 13, 2026, 9:20 PM UTC