How to set up gitlab.nvim with a personal access token?

Create a .gitlab.nvim file in your project root with auth_token=your_token, or set the GITLAB_TOKEN environment variable. Details are in the Connecting to Gitlab section of the README.

gitlab.nvim vs other GitLab plugins for Neovim?

gitlab.nvim is more feature-rich for MR and pipeline management compared to general Git plugins like fugitive. It specifically handles discussions, approvals, and CI/CD jobs, as outlined in its key features.

Can gitlab.nvim work with self-hosted GitLab instances?

Yes, provide a GITLAB_URL environment variable or gitlab_url in the .gitlab.nvim file to point to your self-hosted instance. This is optional and covered in the Connecting to Gitlab section.

How to create a merge request using gitlab.nvim?

Use the global keybinding 'glC' or call require('gitlab').choose_merge_request() in Lua. This creates an MR for the current branch, as described in the Quick Start and Keybindings sections.

What if the build step fails during installation?

Ensure Go is installed and up to date (>=1.25.1). The build function requires it, and errors may occur if Go is missing or incompatible, per the Requirements and Installation notes.

Does gitlab.nvim support GitHub or other Git services?

No, it is exclusively designed for GitLab. For other platforms, you would need alternative plugins, as there is no mention of cross-platform support in the README.

Open-Awesome

Categories Alternatives Stacks Self-Hosted Explore

Open-Awesome

Terms Privacy About GitHub RSS

GitLab.nvim — Neovim GitLab Integration Plugin | Open Awesome

GitLab.nvim

GitLab.nvim

MITLuav4.1.1

A Neovim plugin for managing GitLab merge requests, discussions, and pipelines directly from the editor.

GitHub

What is GitLab.nvim?

gitlab.nvim is a Neovim plugin that allows developers to interact with GitLab merge requests, discussions, and pipelines directly from within the editor. It solves the problem of context switching by integrating GitLab's code review and collaboration features into Neovim, enabling seamless management of MRs, comments, and CI/CD jobs without leaving the editor.

Target Audience

Neovim users who work with GitLab for version control and code reviews, particularly developers and teams looking to streamline their review workflow within the editor.

Value Proposition

Developers choose gitlab.nvim for its deep integration with Neovim, reducing context switching and improving productivity during code reviews. Its unique selling point is the ability to handle complex GitLab workflows—like managing discussions, approvals, and pipelines—entirely within the editor environment.

Overview

Manage Gitlab resources in Neovim

Use Cases

Best For

Reviewing GitLab merge requests without leaving Neovim

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

381 stars60 forks0 contributors

Managing code review discussions and comments in the editor

Handling GitLab CI/CD pipeline jobs from Neovim

Streamlining MR creation, approval, and merging workflows

Reducing context switching during development and code review

Integrating GitLab features into a Neovim-centric workflow

Not Ideal For

Teams using GitHub, Bitbucket, or other non-GitLab version control systems
Developers who prefer web-based or GUI tools for code reviews over terminal/editor integration
Environments where Neovim is not the primary editor, such as those standardized on VS Code or JetBrains IDEs
Projects requiring advanced GitLab features beyond MRs and pipelines, like extensive issue tracking or wiki management

Pros & Cons

Pros

Deep GitLab Integration

Supports the full merge request lifecycle including creation, approval, merging, and discussion handling, as detailed in the Merge Request Management and Discussion Handling features.

Reduced Context Switching

Embeds GitLab's collaborative features directly into Neovim, minimizing the need to switch to a browser during code reviews, aligning with the plugin's stated philosophy.

Extensive Customizable Keybindings

Provides comprehensive default keymaps for global, popup, discussion tree, and reviewer contexts, with options to override them, as shown in the Keybindings section.

Pipeline Management

Enables viewing and managing GitLab CI/CD pipeline jobs from within the editor, a key feature highlighted in the README under Pipeline Integration.

Cons

Go Dependency Required

Requires Go >=1.25.1 to build the binary, adding an extra installation step and potential for build failures, as noted in the Requirements and Installation sections.

Multiple Plugin Dependencies

Relies on several other Neovim plugins like nui.nvim and diffview.nvim, increasing setup complexity and potential conflicts, as listed in the dependencies.

GitLab-Only Support

Exclusively integrates with GitLab, making it unsuitable for teams using other Git hosting platforms, with no mention of support for services like GitHub.