From 382952a9e1e033d9d9ba2383c7b1bb24299ee001 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Fri, 24 Apr 2026 01:42:14 +0100 Subject: [PATCH] docs: mark auto-response non-blocking --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index eb183b161c1..7d3565f537a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -95,8 +95,8 @@ Scoped guides: - Before closing an issue/PR: add a comment explaining why, usually duplicate/invalid, with the canonical issue/PR when relevant. - PR links: `gh pr list --state open --search '' --json number,title,updatedAt,headRefName --limit 20`; use `gh pr view --json number,title,body,closingIssuesReferences,files,statusCheckRollup,reviewDecision` only after shortlist. - CI polling: keep full `gh` capability, but request only needed fields. Known run status: `gh api repos///actions/runs/ --jq '{status,conclusion,head_sha,updated_at,name,path}'`. -- Non-blocking background workflows: `Docs Sync Publish Repo`, `Docs Agent`, and `Test Performance Agent` are service/agent work. Do not wait on, rerun, or fix them during normal push/PR verification unless the user explicitly asks or the task is about those workflows. Report them as background if mentioned. -- `/landpr` CI wait scope: do not idle on pending `check-docs`. Treat docs as local proof unless `check-docs` already failed with a relevant, actionable error. If required product/code gates and touched-surface local gates are green, proceed without waiting for docs-only CI. +- Non-blocking background workflows: `Auto response`, `Docs Sync Publish Repo`, `Docs Agent`, and `Test Performance Agent` are service/agent work. Do not wait on, rerun, or fix them during normal push/PR verification unless the user explicitly asks or the task is about those workflows. Report them as background if mentioned. +- `/landpr` CI wait scope: do not idle on pending `auto-response`/`Auto response` or `check-docs`. Treat docs as local proof unless `check-docs` already failed with a relevant, actionable error. If required product/code gates and touched-surface local gates are green, proceed without waiting for docs-only or auto-response automation. - Waiting: poll lightly, usually 30-60s backoff. Fetch jobs/logs/artifacts only after completion/failure or when job detail is needed; avoid repeated workflow + run + jobs loops. ## Gates