gitlab.nvim

This Neovim plugin is designed to make it easy to review Gitlab MRs from within the editor. This means you can do things like:

• Create, edit, and delete comments on an MR
• Reply to exisiting comments
• Read MR summaries
• Approve an MR
• Revoke approval for an MR

edited.mp4

Requirements

• Go
• make (for install)
• nui.nvim
• plenary.nvim

Installation

You'll need to have an environment variable available in your shell that you use to authenticate with Gitlab's API. It should look like this:

export GITLAB_TOKEN="your_gitlab_token"

Then install the plugin. Here's what it looks like with Lazy:

return {
  "harrisoncramer/gitlab.nvim",
  dependencies = {
    "MunifTanjim/nui.nvim",
    "nvim-lua/plenary.nvim"
  },
  build = function () require("gitlab").build() end, -- Builds the Go binary
  config = function()
    require("gitlab").setup()
  end,
}

And with Packer:

use {
  'harrisoncramer/gitlab.nvim',
  requires = {
    "MunifTanjim/nui.nvim",
    "nvim-lua/plenary.nvim"
  },
  run = function() require("gitlab").build() end,
  config = function()
    require("gitlab").setup()
  end,
}

Configuring per Gitlab Repository

By default, the plugin will not connect to a gitlab repository. You must add a .gitlab.nvim file to the root of your directory. The plugin will read that file and use it as the project ID. The file should only contain the ID of the project:

112415

The tool will look for and interact with MRs against a "main" branch. You can configure this by passing in the base_branch option:

require('gitlab').setup({ base_branch = 'master' })

If you are using main as your branch and you add a .gitlab.nvim configuration file, you can call an empty setup function and the plugin will work:

require('gitlab').setup()

Here is the default setup function:

require("gitlab").setup({
  base_branch = "main",
  port = 20136, -- The port of the Go server, which runs in the background
  keymaps = {
    popup = { -- The popup for comment creation, editing, and replying
      exit = "<Esc>",
      perform_action = "<leader>s", -- Once in normal mode, does action
    },
    discussion_tree = { -- The discussion tree that holds all comments
      jump_to_location = "o",
      edit_comment = "e",
      delete_comment = "dd",
      reply_to_comment = "r",
      toggle_node = "t",
    },
    dialogue = { -- The confirmation dialogue for deleting comments
      focus_next = { "j", "<Down>", "<Tab>" },
      focus_prev = { "k", "<Up>", "<S-Tab>" },
      close = { "<Esc>", "<C-c>" },
      submit = { "<CR>", "<Space>" },
    }
  }
})

Usage

First, check out the branch that you want to review locally.

git checkout feature-branch

Then open Neovim and the reviewer will be initialized. The project_id you specify in your configuration file must match the project_id of the Gitlab project your terminal is inside of. The summary command will pull down the MR description into a buffer so that you can read it:

require("gitlab").summary()

The approve command will approve the merge request for the current branch:

require("gitlab").approve()

The revoke command will revoke approval for the merge request for the current branch:

require("gitlab").revoke()

The comment command will open up a NUI popover that will allow you to create a Gitlab comment on the current line. To send the comment, use <leader>s while the comment popup is open:

require("gitlab").comment()

Discussions

Gitlab groups threads of notes together into "disucssions." To get a list of all the discussions for the current MR, use the list_discussions command. This command will open up a split view of all the comments on the current merge request. You can jump to the comment location by using the o key in the tree buffer, and you can reply to a thread by using the r keybinding in the tree buffer:

require("gitlab").list_discussions()

Within the discussion tree, there are several functions that you can call, however, it's better to use the keybindings provided in the setup function. If you want to call them manually, they are:

require("gitlab").delete_comment()
require("gitlab").edit_comment()
require("gitlab").reply()

Keybindings

The plugin does not set up any keybindings outside of these buffers, you need to set them up yourself. Here's what I'm using:

local gitlab = require("gitlab")
vim.keymap.set("n", "<leader>gls", gitlab.summary)
vim.keymap.set("n", "<leader>glA", gitlab.approve)
vim.keymap.set("n", "<leader>glR", gitlab.revoke)
vim.keymap.set("n", "<leader>glc", gitlab.create_comment)
vim.keymap.set("n", "<leader>gld", gitlab.list_discussions)

Diff Views

This plugin does not provide you with a diff view out of the box for viewing changes. That is already handled by other plugins. I highly recommend using Diffview to see which files have changed in an MR. This is the function that I'm using to accomplish this:

-- Review changes against develop (will break if no develop branch present)
vim.keymap.set("n", "<leader>gR", function()
  local isDiff = vim.fn.getwinvar(nil, "&diff")
  local bufName = vim.api.nvim_buf_get_name(0)
  if isDiff ~= 0 or u.string_starts(bufName, "diff") then
    vim.cmd.tabclose()
    vim.cmd.tabprev()
  else
    vim.cmd.DiffviewOpen("main")
  end
end)

Which looks like this in my editor:

This is useful if you plan to leave comments on the diff, because this plugin currently only supports leaving comments on lines that have been added or modified. I'm currenly working on adding functionality to allow users to leave comments on any lines, including those that have been deleted or untouched.