Add top-of-conversation autotest status indicator with jump-to-block behavior - #2
Merged
Merged
Conversation
Copilot
AI
changed the title
[WIP] Add autotest status block or indicator at the top
Add top-of-conversation autotest status indicator with jump-to-block behavior
Jun 2, 2026
The original implementation searched timeline items for the word "autotest"; verified against a real PR's DOM, that finds nothing because the checks live in the merge box (a sibling of the timeline), so the indicator never rendered. Replace it with checks.js, which locates the merge/checks box and aggregates the per-check aria-labels into one overall passing/failing/running state, and have the indicator scroll to that box. Also guards against a mutation-observer feedback loop by only writing to the DOM when the status key changes. Covered by 11 unit tests and validated against the captured DOM (17 checks -> running). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Long PR timelines make it costly to find autotest results after reversing comments. This change surfaces autotest state near the PR description area and provides a one-click jump to the underlying timeline entry.
Top-level autotest signal on Conversation pages
#pr-reverse-comments-autotest-status) above the timeline container when anautotesttimeline item is present.Status derivation and visual state
✓ Autotest passing✗ Autotest failing• Autotest running• Autotest statusNavigation and lifecycle behavior
Docs