Distillation

Date: Aug 27, 2026

• 🔴 (15:44) User stated that workflow_dispatch must always be allowed for manual recovery.
• 🟡 (15:44) Shared CI poller workflow excerpt shows a cron trigger of */5 * * * *, a check-ci job, and concurrency group ci-status-poller.
• 🟡 (15:44) CI poller workflow comments indicate sentry-release-bot token is used for cross-repository API access, while sentry-internal-app token is used for label changes in the current repository.
• 🟡 (15:44) CI poller examines only issues carrying both ci-pending and accepted labels, queries up to 200 issues, parses repository names from publish: issue titles, and falls back to the issue SHA when branch-HEAD resolution fails.
• 🟡 (15:44) CI poller fetches commit statuses and paginated check runs; it treats completed check runs with conclusions other than success, neutral, or skipped as unsuccessful. It recognizes the case of no check runs/statuses as CI not yet started.
• 🟡 (15:44) CI poller adds ci-ready when CI passes, comments on CI outcomes, and on CI failure removes/handles approval so the author must fix CI and re-add accepted to retry. Failure details include failed check names and failed/error commit-status contexts, with target URLs when available.
• 🟡 (15:44) CI poller includes pending-work and fallback-chain handling: if the CI-check step fails, CI_POLLER_HAS_PENDING is not set; token creation for subsequent behavior is intentionally placed after CI checking so token failure cannot block CI checks; fallback continues checking and restarts the chain on the next run; an attempt limit of 60 is enforced.