Repository navigation
Show merge queue checks in five CI history lanes - #21
Merged
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
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.
Changes
Show CI history in five ordered lanes: PR, main (or the full branch name), merge queue, Daily, and release. Classify
merge_groupbefore workflow name rules so queue checks cannot be swallowed by Nightly or Release. Remove called, other-workflow, and unknown-trigger rows and their fallback run links while continuing to store every collected run.Rebuild older lane snapshots from existing records without fetching artifacts. Keep the overview and CI page consistent, update explanatory text and documentation, and bump the UI cache version to
20261020.1. Success-rate calculations, per-day ordering, Actions queries, artifact limits, and collection triggers stay unchanged.Preserve the original fixture run IDs used to associate E2E records with their branch while adding CI examples.
Validation
PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s tests -v— 166 passed (10.828s).node .e2e/node_modules/playwright/cli.js test --config test/playwright.config.cjs— 27 passed (55.3s).Browser coverage checks five-row order, removed categories, queue links opening in a new tab, empty queues, release-branch Nightly placement, and desktop/390px layouts without page overflow. Unit coverage verifies that old snapshots rebuild without artifact requests and retain hidden runs in history.