What’s one GitHub feature you wish worked differently and why? #176582
-
Select Topic AreaQuestion BodyTell us one GitHub feature you use often that frustrates you (Notifications, PR review UX, Codespaces, etc.). Describe the pain, and suggest a concrete improvement. #114819 #feedbak |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Seeing inline suggestions by default in Codespaces after initiating a Copilot chat. This is frustrating because the suggestions are usually way too verbose and not what I'm trying to write, and I like to learn by trying to type it myself. I would love to have this off by default. I have found a setting to disable this (very difficult to find), but the next time I use the Copilot chat, it comes back on! Very annoying! I would like a GUI solution to disable inline Copilot suggestions across all Codespaces and repos by default, that doesn't become re-enabled without my consent. |
Beta Was this translation helpful? Give feedback.
TL;DR: The PR review UX needs a “Review Sessions” workflow: group comments into a single review session with priority (blocking vs suggestion), batch-apply suggestions, and a built-in ephemeral preview so reviewers and authors can test changes without juggling local branches.
Problem I run into (real pain):
Large PRs generate dozens of inline comments across many files. It’s hard to keep review context and difficult to tell which comments are blocking vs optional suggestions.
Applying many small suggested changes is repetitive — either the author must manually patch each suggestion, or reviewers need to push a follow-up commit. This creates review churn and fragmented history.
Reviewers a…