Question 1

How do I set up gh.nvim for code reviews?

Accepted Answer

Install git and gh CLI tools, then add gh.nvim and its dependency litee.nvim to your Neovim config using a plugin manager like lazy.nvim, and configure it with optional fzf.lua or Telescope for UI selection, as detailed in the README.

Question 2

gh.nvim vs GitHub web UI: which is better for reviews?

Accepted Answer

gh.nvim is superior for complex reviews needing local context and LSP tools, while the web UI is better for quick reviews, collaborative features like real-time comments, and integrated CI checks without local setup.

Question 3

Can gh.nvim handle private GitHub repositories?

Accepted Answer

Yes, as long as you have authenticated the gh CLI with your GitHub account and have access to the repository, gh.nvim will work with private repos by fetching and checking out the code locally.

Question 4

How to submit a comment on a pull request with gh.nvim?

Accepted Answer

Inside a conversation buffer, use the configured keymap (default <C-s>) to submit comments, and you can draft responses by editing the local code directly before submitting, as per the plugin's keymap settings.

Question 5

What if gh.nvim fails to fetch a pull request?

Accepted Answer

Check your gh CLI authentication and network connection, ensure the repository exists and you have permissions, and verify that the Git remote is correctly added, as the plugin relies on external tools for automation.

Question 6

Are there alternatives to gh.nvim for Neovim?

Accepted Answer

Alternatives include vim-fugitive for basic Git integration and custom scripts, but gh.nvim is specifically designed for GitHub code reviews with local context and automation, though it has more dependencies.

gh.nvim

What is gh.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions