Skip to content

Use a var instead of a secret for reviewer weights - #9357

Merged
tlively merged 1 commit into
mainfrom
tlively-patch-1
Nov 6, 2026
Merged

tlively merged 1 commit into
mainfrom
tlively-patch-1

Conversation

@tlively

@tlively tlively commented Nov 6, 2026

Copy link
Copy Markdown
Member

This will make the weights public, but also viewable and editable, which seems useful.

This will make the weights public, but also viewable and editable, which seems useful.
@tlively
tlively marked this pull request as ready for review November 6, 2026 22:20
@tlively
tlively requested a review from a team as a code owner November 6, 2026 22:20
@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@tlively
tlively merged commit 526237a into main Nov 6, 2026
18 of 20 checks passed
@tlively
tlively deleted the tlively-patch-1 branch November 6, 2026 22:34
tlively added a commit that referenced this pull request Nov 9, 2026
The single GraphQL query in scripts/assign_reviewer.py fetched 100
recent PRs with three nested first: 100 connections (latestReviews,
reviewRequests, and timelineItems) in one request, which intermittently
exceeded GitHub's 10-second GraphQL execution timeout and failed with
HTTP 502 (such as on PR #9357 and PR #9368).

Split the initial team and target PR lookup into SETUP_QUERY so closed,
draft, or already-assigned PRs exit early without fetching PR history,
paginate RECENT_PRS_QUERY across two pages of 50 PRs with first: 20 on
latestReviews and reviewRequests, and retry transient GitHub API 5xx
errors in gh_api with exponential backoff.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants