Skip to content

Retry transient slash-command provenance checks - #59313

Draft
pelikhan with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-pre-activation-error-handling
Draft

Retry transient slash-command provenance checks#59313
pelikhan with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-pre-activation-error-handling

Conversation

Copilot AI commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Centralized slash-command workflows treated transient GitHub API failures during PR provenance checks as authorization denials, silently skipping downstream execution and leaving status comments unresolved.

  • Retry transient failures
    • Wrap PR provenance lookup with the existing retry utility.
    • Retry 5xx, rate-limit, timeout, and network failures with bounded exponential backoff.
  • Preserve security behavior
    • Continue failing closed after retries are exhausted.
    • Do not retry permanent API failures or alter fork-provenance validation.
  • Regression coverage
    • Cover recovery from a transient 500 response.
    • Cover fail-closed behavior after retry exhaustion.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix pre_activation handling of transient GitHub API errors Retry transient slash-command provenance checks Sep 7, 2026
Copilot AI requested a review from pelikhan September 7, 2026 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants