fix(ci): add load more for repo runs#196
Merged
barrettruth merged 1 commit intomainfrom Apr 12, 2026
Merged
Conversation
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
1 participant
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.
Problem
Repo CI runs were already fetched with a hard cap from
display.limits.runs, but the picker did not expose that limit. It looked like the first page was the whole list, and there was no way to request more runs from the picker.Solution
Use the existing picker pagination pattern for repo CI runs: fetch one extra run, show a
Load more...row when more runs are available, and request a larger explicit run limit when that row is activated. The PR also updates vimdoc to explain that:Forge cirespectsdisplay.limits.runsand exposesLoad more...when more runs exist.