Distillation

Date: Aug 27, 2026

• 🟡 (21:11) .github/workflows/auto-approve.yml is named auto-approve non-sdks; it triggers only on newly opened issues (issues.types: [opened]), grants contents: read, and runs auto-approve on ubuntu-latest only when github.actor is sentry-release-bot[bot] or getsantry[bot] and the issue title starts with publish: .
• 🟡 (21:11) .github/workflows/auto-approve.yml checks out only auto-approve-repos.txt using actions/checkout@v4, sparse-checkout: auto-approve-repos.txt, and sparse-checkout-cone-mode: false; it obtains an app token via actions/create-github-app-token@v3 using vars.SENTRY_INTERNAL_APP_ID and secrets.SENTRY_INTERNAL_APP_PRIVATE_KEY.
• 🟡 (21:11) .github/workflows/auto-approve.yml supplies GH_TOKEN from steps.token.outputs.token, ISSUE_TITLE from github.event.issue.title, and ISSUE_URL from github.event.issue.html_url; its shell step extracts the text between publish: and the final @ via sed -n 's/^publish: \(.*\)@.*/\1/p', then runs gh issue edit "$ISSUE_URL" --add-label accepted only when that exact extracted repository string is a line in auto-approve-repos.txt.
• 🟡 (21:12) GitHub REST API documentation states that issue and pull-request activity events can be retrieved through Issues endpoints; the repository-wide issue-events endpoint is GET /repos/{owner}/{repo}/issues/events, with case-insensitive required owner and repo, optional per_page (default 30, maximum 100), and optional page (default 1).
• 🟡 (21:12) GitHub REST API documentation recommends standard headers Authorization: Bearer <YOUR-TOKEN>, Accept: application/vnd.github+json, and X-GitHub-Api-Version: 2026-03-10 for most endpoints.