Increase Q workflow timeout to prevent Copilot engine timeout failures

[Copilot]

The Q workflow is failing on long investigations because the Copilot execution step hits the 15-minute ceiling. This change raises the workflow timeout budget so runs can complete instead of terminating mid-analysis.

• Timeout budget update

  • Increased Q workflow timeout-minutes from 15 to 30 in source workflow config:
    • .github/workflows/q.md

• Compiled workflow sync

  • Recompiled lockfile to carry the same timeout into generated execution config:
    • .github/workflows/q.lock.yml

• Effective runtime change

  • The generated Execute GitHub Copilot CLI step now uses:

    timeout-minutes: 30

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/graphql
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw GOMOD GOMODCACHE 726187/b396/impoGO111MODULE /opt�� che/go-build/cc/GOINSECURE --check 64/bin/go --ignore-path .prettierignore 64/bin/go /opt/hostedtoolcGOPROXY (http block)
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw GOMOD GOMODCACHE 726187/b443/impoGO111MODULE -c che/go-build/b7/GOINSECURE GOPROXY 64/bin/go GOSUMDB GOWORK 64/bin/go go (http block)
  • Triggering command: /usr/bin/gh /usr/bin/gh api graphql -f query=query($owner: String!, $name: String!) { repository(owner: $owner, name: $name) { hasDiscussionsEnabled } } -f owner=github -f name=gh-aw GOWORK run-script/lib/n-json sh -c "prettier" --cheGOINSECURE node 64/bin/go prettier --write 64/bin/go go (http block)
• https://api.github.com/repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b
  • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq [.object.sha, .object.type] | @tsv --porcelain node $name) { hasDiscussionsEnabled } } --write ../../../**/*.js--norc 64/bin/go go env -json GO111MODULE 64/bin/go GOINSECURE GOMOD GOMODCACHE go (http block)
  • Triggering command: /usr/bin/gh gh api /repos/astral-sh/setup-uv/git/ref/tags/eac588ad8def6316056a12d4907a9d4d84ff7a3b --jq [.object.sha, .object.type] | @tsv (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)

[Copilot]

Pull request overview

Updates the Q agentic workflow to allow longer Copilot investigations to complete without hitting the prior 15-minute execution ceiling.

Changes:

• Increased Q workflow timeout-minutes from 15 to 30 in the source workflow definition.
• Recompiled the generated workflow lockfile so the Copilot execution step uses the updated 30-minute timeout.
• Updated the generated runtime timeout env (GH_AW_TIMEOUT_MINUTES) to match.

Show a summary per file

File	Description
.github/workflows/q.md	Raises the workflow timeout budget to 30 minutes in the source frontmatter.
.github/workflows/q.lock.yml	Syncs generated workflow to apply the 30-minute timeout to the Copilot execution step and related runtime env.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0