Support for PR reviews inside the editor - like Github PR review extension VS code

[kunaaal13]

Zed is already a fast, focused editor that’s great for deep work. But code review is still one of the most frequent developer tasks, and currently it requires switching contexts — jumping between GitHub’s web UI or another editor.

An integrated PR review experience inside Zed would:

• Keep the entire workflow in one environment
• Improve focus and productivity
• Make Zed more appealing for teams that collaborate through GitHub

🚀 Proposed Features

• Browse and filter open PRs from linked GitHub repositories
• Checkout PR branches directly from the UI
• Inline comment threads shown alongside diffs
• Submit comments, approve, request changes, or merge PRs without leaving Zed
• Diff viewer for file-by-file review with syntax highlighting and minimaps
• Optional PR summary sidebar showing metadata (author, reviewers, CI status, etc.)

🧩 Possible Implementation Ideas

• Implement as an extension using Zed’s upcoming plugin system (if applicable)
• Use the GitHub REST API / GraphQL API for fetching PR data
• Integrate with Zed’s existing Git / Diff system for smooth navigation and commenting

💡 Inspiration
VS Code – GitHub Pull Requests and Issues Extension
JetBrains IDEs GitHub Integration

✅ Benefits

• Streamlined workflow for developers using Zed daily
• No need to context-switch between browser and editor
• Great for open-source contributors and team-based code review

🗣️ Example Use Case

“I open Zed, connect my GitHub account, see a list of open PRs in the sidebar, click on one, review diffs inline, leave comments, and approve — all without leaving Zed.”

[JonGretar]

The thing is. I would rather that they focus on finishing the git implementation and adding jj support before the start adding some specific workflows from specific services. Many also use Gitlab or other services and do we then add those. That would become utter UI chaos.

It's different for VSCode. Whose main job these days is to sell you GitHub accounts.

So they should not add this at all to core. GitHub, GitLab and others can add this as an extension at a later date.