Repository navigation
Automatically size pull request dashboards - #514
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Pull request dashboard statusMerged · refreshed 2026-11-06 16:42 UTC Status above doesn't look right?
|
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Removing the large-repo setting and flag forwarding disables sizing protection in the pinned stable publisher, causing oversized dashboards to fail publication until the autosizing release is promoted.
1 open issue
What changed in this PR
This PR replaces manual dashboard sizing presets with automatic trimming to fit GitHub’s 65,536-character issue-body limit, while leaving routing and notifications unchanged.
Changes:
- Show all rows, including drafts, when they fit; otherwise trim complete rows from lower-priority sections first.
- Preserve section headings and exact omission counts, and add a truncation warning.
- Remove
large_repoconfiguration and CLI handling, with updated documentation and tests.
| File | Description |
|---|---|
pull-request-dashboard/README.md |
Documents automatic sizing and omission behavior. |
.github/scripts/pull-request-dashboard/test_render.py |
Tests size boundaries, trimming order, and omission notices. |
.github/scripts/pull-request-dashboard/test_publish_dashboard.py |
Updates publisher tests and covers draft-fetch skipping and size guards. |
.github/scripts/pull-request-dashboard/test_owned_execution.py |
Updates configuration fixtures and publisher command assertions. |
.github/scripts/pull-request-dashboard/repositories.json |
Removes collector-contrib’s manual sizing setting. |
.github/scripts/pull-request-dashboard/render.py |
Implements character-budget trimming and section omission tracking. |
.github/scripts/pull-request-dashboard/publish_dashboard.py |
Uses automatic sizing and skips unnecessary draft metadata fetches. |
.github/scripts/pull-request-dashboard/process_queue_batch.py |
Stops forwarding the legacy sizing flag. |
Review effort: Balanced
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
maryliag
approved these changes
Nov 5, 2026
Kielek
approved these changes
Nov 6, 2026
mx-psi
approved these changes
Nov 6, 2026
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.

Automatically fit pull request dashboards within GitHub's 65,536-character issue-body limit. Show all PRs, including drafts, whenever they fit, without a fixed 100-row cap.
When needed, trim complete rows from bottom to top: drafts, unknown PRs, transient GitHub failures, PRs waiting on authors, reviewers, then maintainers. Exhaust each lower section before trimming the next, preserving the longest-waiting PRs within each section.
Add an overall truncation warning and keep section headings with exact omission counts even when every row is hidden. Routing and notifications are unchanged.
Roll out through canary before stable promotion. Retain the deprecated
large_reposetting and flag forwarding so pinned stable publishers keep their size protection; the automatic publisher accepts--large-repoas a no-op. Remove that compatibility support after promotion.