[Copilot]

The activation and conclusion jobs failed when lock-for-agent was enabled without ai-reaction configured, because the GitHub API's issues.lock() and issues.unlock() endpoints require write permissions.

Changes

• pkg/workflow/compiler_jobs.go: Added conditional issues: write permission to activation job when lock-for-agent: true, independent of reaction configuration
• pkg/workflow/lock_for_agent_test.go: Added permission assertions to verify correct behavior with and without reactions

Example

Before:

# lock-for-agent: true, no reaction
activation:
  permissions:
    contents: read
    # Missing issues: write → API call fails

After:

# lock-for-agent: true, no reaction  
activation:
  permissions:
    contents: read
    issues: write  # Added for lock API

The conclusion job already had correct permissions via NewPermissionsContentsReadIssuesWritePRWriteDiscussionsWrite().

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/user
  • Triggering command: /usr/bin/gh gh api user --jq .login g_.a GO111MODULE /opt/hostedtoolcache/go/1.25.0/x64/bin/go GOINSECURE GOMOD GOMODCACHE go b-ag�� GmkEpiFk4 GO111MODULE /opt/hostedtoolcache/go/1.25.0/x64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login -json GO111MODULE ache/go/1.25.0/x64/pkg/tool/linux_amd64/asm GOINSECURE GOMOD GOMODCACHE ache/go/1.25.0/x64/pkg/tool/linux_amd64/asm env tags/v5 GO111MODULE /opt/hostedtoolcache/go/1.25.0/x64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
  • Triggering command: /usr/bin/gh gh api user --jq .login d-artifact.git GO111MODULE e/git GOINSECURE GOMOD GOMODCACHE e/git env -json om/different-owner/different-repo 1/x64/bin/node GOINSECURE GOMOD GOMODCACHE go (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

The activation and conclusion jobs should have "issue: write" permission when locking is needed.

Reference: https://github.com/githubnext/gh-aw/actions/runs/20168343382/job/57897233312

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.