Feature Request: Add Pull Request (PR) Integration to LazyGit

[PiyushShiv26]

Describe the feature you'd like

I recently started using Neovim and switched over from VS Code. One of the features I really enjoyed in VS Code was its built-in source control view, especially how it handled GitHub pull requests directly within the editor.

When I discovered LazyGit, it instantly became my go-to tool — it’s lightweight, intuitive, and honestly even more enjoyable to use than VS Code’s source control. The only thing I’ve found missing is the ability to interact with pull requests directly from LazyGit.

It would be amazing to have PR-related features like:

• Viewing open pull requests in the current repo
• Checking out a PR branch
• Creating a new PR from the current branch
• Viewing PR status, comments, and merge conflicts

Having this integrated into LazyGit would make it a truly complete Git experience within the terminal.

---

Describe alternatives you've considered

I’ve tried using gh (the GitHub CLI) alongside LazyGit to manage PRs, but switching contexts breaks the otherwise smooth, single-interface workflow LazyGit provides. A built-in (or even optional) PR integration would make the experience seamless.

---

Additional context

This could work either through direct GitHub/GitLab API integration or via external tools like gh — maybe LazyGit could detect if gh is installed and use it under the hood.

I know there are ways to add custom commands, but having native support for PR operations would make it accessible to more users out of the box and strengthen LazyGit’s position as a complete terminal Git UI.

Thanks for all the work you’ve put into this project — it’s seriously one of the best developer tools I’ve come across!

[stefanhaller]

This has come up before (always a good idea to search for existing issues before filing new ones...).

#900 has some thoughts about this. Also, there's #2781 which was a prototype implementation of showing PR numbers in the branches list. It conflicts heavily with current master.

[PiyushShiv26]

Thanks for the pointers! I went through both issues, #900 and #2781, and yeah, they touch on similar ideas.

My initial thought was mainly around making PR interactions (viewing, checking out, maybe even creating PRs) more accessible directly from LazyGit, similar to how it handles commits and branches today.

The prototype in #2781 looks like a great starting point. I’m curious, would there be interest in revisiting that work or exploring a lighter integration (maybe starting with just listing and checking out PR branches via the GitHub CLI or API)?

I’d be happy to help explore or test an approach if it’s something worth reviving.

[stefanhaller]

viewing, checking out, maybe even creating PRs

There's gh dash for that, and I'm not sure we should try and incorporate that into lazygit. I'm a fan of tools that focus on one thing and do it well.

Creating PRs is available from within lazygit though, with the o keybinding on a branch. It takes you to github, which is maybe not what you meant, but I absolutely don't think we should replicate github's UI for creating the PR in lazygit, if that's what you had in mind.

Viewing PRs can easily be done with custom commands (also in the sense that it takes you to the github page for the PR), if you know which branches have an associated PR. So the display of a PR next to a branch is really all that's missing (for me, personally). That's what #2781 does, and yes, I would find it useful to revive that work. I don't have time for that myself though (this year at least), and I probably won't have much time to help others with it, either.

[PiyushShiv26]

Thanks a lot for the detailed response — that makes sense. I totally agree with keeping LazyGit focused and not overlapping with gh dash.

I think the PR display alongside branches (like in #2781) would still be a nice addition, even if it’s minimal. I’ll keep this issue open for visibility, in case anyone else wants to pick it up or revive that prototype.

Appreciate the clarification!

[dlvhdr]

Hey, I'm the author of gh dash.
I also like the separation of concerns between lazygit and dash but I think an interface point would be nice to have.
So I'm also in favor of displaying the PR #/name/title next to the branch. That way you at least know which branch is pushed to github and know you can further act on it in github / dash.
I'm happy to brainstorm more deep integration as well.
In general, it would be awesome to have the equivalent of the pipe (|) for TUIs to let them interface easily with each other.

[stefanhaller]

Hi @dlvhdr, good to hear from you.

So I'm also in favor of displaying the PR #/name/title next to the branch.

Displaying more data in the branches panel is really tricky, because that panel is already so full of information. Especially when you use the gui.showDivergenceFromBaseBranch: arrowAndNumber, which I would really like to make the default, but didn't dare yet because it makes the display so much more noisy. I feel that adding the PR number or name makes it simply too crowded and hard to read.

But yes, I also want to see an indication which branches have a PR. I rebased #2781 onto master yesterday, so you can try how that looks. I chose to simply replace the normal branch icon with a colored github icon; it's a bit subtle, but does the job for me.

Then we could show some more information about the PR in the main view on the right (above the branch log) when a branch is selected; I added a quick hacky commit to do that, looks like this:

The yellow PR title is a hyperlink, clicking it takes you to the PR in the browser.

I'm not a skilled UI designer, so if anybody has ideas how to improve all this, I'm open to suggestions. But functionality wise, I think this is all I need.

[dlvhdr]

@stefanhaller this is awesome!
I get the space constrains, the icon solution is perfect. It lets me know exactly enough info and I can see the title in the side pane.
I played around with the styling a bit, but the code is hardcoded and I couldn't figure out how to combine fg and bg styles. So if you like the style I went for feel free to make the fixes.

dlvhdr#1

• I changed the title from yellow to white as yellow for me conveys a warning
• The pill should eventually look like so (for open PRs):
• I added a github icon so people know where this info came from
• Could be there are better solutions but I added a border to further separate the title from the rest of the content
• I introduced another color for draft PRs
• I changed the color of open PRs to blue

[stefanhaller]

I added a commit that iterates on the UI a bit in this direction, albeit without the pill for now. We can probably still improve this further, but I'd say the UI design isn't the biggest problem that we have left to solve for this whole thing.

BTW, we have a general UI design constraint when it comes to colors, which is that we are limiting ourselves to the standard terminal palette colors for now. The reason is that for hex colors you can't know how well they fit with whatever palette configuration is being used, so we stay away from them as much as we can (I think file icons is pretty much the only case where we use them right now). Of course, hex colors would give us a lot more flexibility, and allow for a much slicker design probably, but I'd say if we want to use them, then we need to go in fully on configurable themes for everything (including the background color), and I don't want to go this route as long as we can avoid it. (I'm also not sure how well custom pagers would fit into it.)

I changed the color of open PRs to blue

Why? I see that gh dash does this too, but on github, open PRs are green.

[dlvhdr]

Ohh my bad. It's because I set it to red/green color blindness