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:
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.
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.
Related issues: