feat: support jumping with g+G in incident views - #426
Merged
Merged
Conversation
Tests Generated by: Claude Code (opus 4.6)
clcollins
added a commit
that referenced
this pull request
Aug 11, 2026
PR #426 (g/G navigation in incident viewer) was silently reverted when PR #419's rebase resolved a conflict by keeping only the #419 side. CI could not catch it because the feature and its test were removed together. This restores all three changes verbatim from PR #426. Co-authored-by: agent-bot <agent-bot@localhost> Co-authored-by: Claude Opus 4.6 <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.
What type of PR is this?
(bug/feature/cleanup/documentation)
Feature
What this PR does / Why we need it?
This PR extends the vim-style jump motions (g/G) to the tabs within the incident viewer. Previously these keystrokes were ignored. This allows quickly scrolling SLs and other incident contextual information.
This PR also fixes the
getlintMakefile recipe to check for golangci-lint the same way it is invoked inlint. Previously, having golangci-lint installed to a location like/usr/binwould fail to runlint.Which Jira/Github issue(s) does this PR fix?
Resolves #
N/A
Special notes for your reviewer
Pre-checks (if applicable)