github / github/app

Show annotation counts and next/previous navigation in the file browser

オープン
#2,928 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
triage
主要言語
言語のデータがありません
スター
2.1k
フォーク
153
PR マージ指標
30日以内にマージされた PR はありません

説明

### Feature summary

Provide a quick overview of file annotations and easily navigate to them.

### What problem are you trying to solve?

When a session produces inline annotations (review findings, agent comments) across a diff, there's no way to tell at a glance how many exist or where they are. Today you have to open each file and scroll to find them. On a change touching a dozen files with a handful of annotations, this means:

- **No visible count** — you can't tell whether a file has 0 or 8 annotations without opening it.
- **No total** — you don't know how much review feedback is outstanding overall.
- **No jump** — there's no "go to next annotation" affordance, so triaging means manual scrolling per file.

The result is that annotations get missed, and reviewing them is slower than it should be.

### Proposed solution

1. **Per-file badge in the file browser** — each file row shows a count of its annotations, styled by the highest severity present (blocking / warning / info). Files with zero annotations show no badge.
2. **Aggregate count in the header** — a total like `12 annotations across 5 files`, with unresolved vs. resolved broken out if resolution state exists.
3. **Next/previous navigation** — prev/next controls (plus keyboard shortcuts, e.g. `n` / `Shift+N`) that walk annotations in file-then-line order, crossing file boundaries automatically: opens the target file, scrolls the annotation into view, and focuses it.
4. **Filtering** — optionally collapse the browser to only files that have annotations, and/or filter by severity.

### Workflow impact

_No response_

### Installation context

_No response_

### Additional context

_No response_

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

No files, tests, or entry points are named. Start by locating the file browser and the existing annotation data flow, then determine how counts, severity, resolution, navigation, and filtering fit together. Done means per-file and aggregate counts are visible and users can move through annotations across files with the specified navigation behavior.

索引モデルが issue の本文から書いたものです。

評価

領域
desktop
issue の種類
機能追加
難易度
5/5
見積もり時間
1週間以上
活発さ
活発
明瞭さ
おおむね明確
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。