Dashboard › publish › Distillation
d836ac9d-713f-474b-9195-93287170f549["lore_tm_v1_fxXpxDbnGz4GQUaxR0dZ3Rp1MxPW-Y8YxAXhLlAVRME"]
.github/workflows/ci-poller.yml lines 99–113 lists up to 200 open issues carrying both ci-pending and accepted; when none exist, it prints No ci-pending + accepted issues found. and exits successfully..github/workflows/ci-poller.yml lines 170–217 extracts a 40-character commit SHA from the issue body’s /commit/{SHA}/checks link, discovers the release branch from the original commit’s first check suite, resolves that branch’s current HEAD, and falls back to the issue SHA if either lookup fails; if the branch moved, it replaces the old SHA in the issue body..github/workflows/ci-poller.yml use the Sentry Release Bot token through gh_api_release(), while issue-label changes use the Sentry Internal App token; gh_api_release() captures stderr/stdout, warns on API failures including 404s, and returns the original nonzero exit code..github/workflows/ci-poller.yml lines 221–267 fetches combined commit status and paginated check runs; API failure skips the issue rather than deriving state from partial data. It treats success, neutral, and skipped check conclusions as passing and treats failure, cancelled, timed_out, action_required, stale, and startup_failure as unsuccessful..github/workflows/ci-poller.yml requires at least one check run or commit status, no pending check runs, no unsuccessful check runs, and either combined commit status success or zero reported commit statuses for repositories that use check runs only..github/workflows/ci-poller.yml removes ci-pending, adds ci-ready, retains accepted, and comments CI checks passed for ${repo}@${version}. Publishing is starting now..github/workflows/ci-poller.yml removes ci-pending and accepted, adds ci-failed, lists the failed check names, links to https://github.com/${repo}/commit/${sha}/checks/, and instructs the author to re-add accepted after fixing CI.failure, .github/workflows/ci-poller.yml removes ci-pending and accepted, adds ci-failed, and comments with each status in state failure or error, including its target_url when available..github/workflows/ci-poller.yml lines 395–435 always recounts open issues with both ci-pending and accepted, obtains a token using CI_POLLER_APP_CLIENT_ID and CI_POLLER_APP_PRIVATE_KEY, and synchronizes repository variable CI_POLLER_HAS_PENDING to "true" when work remains or "false" when none remains.ci-status-poller with cancel-in-progress: false; self-dispatch is intended to provide approximately 30–60 seconds between checks, permits one running and one queued workflow, and relies on the */5 * * * * cron fallback because GitHub cron may drift to 30–40 minutes under load.