[Desktop] Pinned sessions should get their own section at the top of the left nav when grouping by status
まだ誰も着手していません。
- 主要言語
- Shell
- スター
- 11.2k
- フォーク
- 1.9k
- 平均マージ
- 14時間 16分
- マージ済み PR(30日)
- 6
説明
Describe the feature or problem you'd like to solve
When the left nav is grouped by session status, pinning a session moves it to the top of whichever status group it currently belongs to. It stays inside that group.
That doesn't give me what pinning is for. The session still moves between groups every time its status changes — top of one group, then top of another, then somewhere else again. So to use the pin, I first have to work out which group the session is in, and only then does being at the top of it help. The pin gives me position within a group, but not a stable place in the nav.
The result is that pinning is least useful exactly when I need it most. I group by status when I have a lot of sessions open, and that's precisely when a session that relocates on every status change is hard to keep track of.
Grouping by project doesn't have this problem — it already gives pinned sessions their own section above the groups. Status grouping is the only view where a pin is confined to a group.
Proposed solution
Hoist pinned sessions into a dedicated Pinned section above the status groups, so a pinned session has one fixed location regardless of its status.
- Pinned sessions appear in the Pinned section only, not also inside their status group.
- Status stays visible on the pinned item, so pinning doesn't cost the information the grouped view exists to provide.
- A status change doesn't move a session out of the section — only Unpin does, returning it to its status group.
- The section is hidden when nothing is pinned.
This is already how grouping by project works — that view puts pinned sessions in their own section above the project groups, rather than pinning them inside a group. Grouping by status is the outlier. It also matches the last-updated view, where the pinned session sits apart at the top and the sorting applies to everything else.
Additional context
Deliberately narrow: this is about where pinned sessions live in the grouped view, not about auto-pinning or any change to what Pin means.
- Operating system: Windows
- GitHub desktop app v1.1.2
Related issues:
- #3969 — Plan status indicators on session list items. Related to keeping status visible on pinned items.
- #3970 — User-defined tags on sessions. If tag grouping ships, pinned sessions would need the same treatment.
- #890 — Folder-Pinned Sessions. Different meaning of "pin" — auto-resuming a session per repo folder in the CLI.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
issue にはファイル名もテスト名も記載されていません。まず、ステータスによるグループ化を行うデスクトップ左ナビゲーションのコードを見つけ、次にプロジェクトによるグループ化ビューと最終更新ビューでピン留めされたセッションがどのように表示されるかを比較します。ピン留めされたセッションが、必要な場合以外は非表示の「ピン留め済み」セクションにのみ表示され、表示上のステータスを維持し、ピン留めを解除するとステータスグループに戻れば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- shell
- 領域
- desktop
- issue の種類
- 機能追加
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 静か
- 明瞭さ
- 明確に書かれている
- 初心者へのやさしさ
- 70/100