Use a single flag to handle all changes for large repo#34
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR simplifies the pull-request-dashboard configuration by collapsing the two separate large-repo tuning knobs (max_rows_per_section and skip_drafts) into a single large_repo boolean. It also introduces a new behavior where webhook-driven runs are skipped for large_repo targets to avoid exhausting the GitHub App's hourly API quota, while scheduled and manual runs still process them.
Changes:
- Replaced
max_rows_per_section/skip_draftswith a singlelarge_repoflag across the Python script, reusable workflow, config, and docs (50-row cap + drafts omitted are now presets behind the flag). - Added a
Check webhook large-repo skipstep that suppresses webhook-triggered refreshes (token minting + dashboard job) for large repos, driven by the trigger event type. - Updated
repositories.jsonandREADME.mdto reflect the consolidated flag and the new triggering behavior.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/scripts/pull-request-dashboard/dashboard.py |
Replaces two CLI args with --large-repo, introduces LARGE_REPO_MAX_ROWS_PER_SECTION = 50, and removes now-obsolete validation. |
.github/workflows/pull-request-dashboard-repo.yml |
Swaps the two reusable-workflow inputs for large_repo and passes --large-repo to the script. |
.github/workflows/pull-request-dashboard.yml |
Adds webhook large-repo skip step and gates token creation / precondition on it; passes large_repo to the matrix job. |
.github/scripts/pull-request-dashboard/repositories.json |
Updates the collector-contrib entry to use large_repo: true. |
pull-request-dashboard/README.md |
Documents the consolidated large_repo field and its rendering + triggering effects. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
mx-psi
approved these changes
Jul 3, 2026
mx-psi
left a comment
Member
There was a problem hiding this comment.
At this point we could call the option "is_collector_contrib" 😅. LGTM!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use a single
large_repovariable to cap the section at 50 PRs, don't show draft PRs and don't get trigger by webhook calls (only hourly and manual).The amount of calls was making the GH API hit the quota