How do I authenticate pipeline.nvim with GitHub?

Set a GITHUB_TOKEN environment variable or use the authenticated gh CLI; the plugin automatically sources the token from gh if available, as per the authentication section.

Does pipeline.nvim work well with GitLab CI?

It's listed as 'fairly untested' in the README, so while basic support exists, it may be buggy and users are encouraged to report issues or contribute fixes.

How to customize the split window layout in pipeline.nvim?

Adjust the split position, size, and win_options in the configuration, such as setting position to 'right' and size to 60 for a sidebar layout, as detailed in the options.

pipeline.nvim vs other Neovim Git plugins like vim-fugitive?

pipeline.nvim specializes in CI/CD pipeline monitoring and dispatch, while vim-fugitive focuses on Git operations; they complement each other but serve different purposes in the workflow.

Is there a way to rerun a failed pipeline job in pipeline.nvim?

No, this feature is currently missing and listed in the ToDo section; users must use external methods like the browser or CLI until it's implemented.

What dependencies are needed for pipeline.nvim installation?

You need either yq installed, or GNU Make and Cargo to build the plugin, which adds steps beyond typical Lua plugins, as mentioned in the dependencies section.

How to integrate pipeline.nvim with lualine?

Add a pipeline component to lualine sections using the provided code snippet, allowing real-time CI status display in your Neovim status bar for enhanced visibility.

Open-Awesome

pipeline.nvim

Lua

A Neovim plugin to view and manage CI/CD pipeline runs (GitHub Actions, GitLab CI) directly within the editor.

GitHub

182 stars12 forks0 contributors

What is pipeline.nvim?

pipeline.nvim is a Neovim plugin that provides direct access to CI/CD pipeline runs from within the editor. It displays the status of GitHub Actions and GitLab CI pipelines, allows dispatching new runs, and integrates with multiple Git remotes. It solves the problem of constantly switching between the editor and browser to check CI/CD status.

Target Audience

Neovim users who regularly work with CI/CD pipelines on GitHub Actions or GitLab CI and want to streamline their workflow.

Value Proposition

Developers choose pipeline.nvim because it eliminates context switching by embedding CI/CD monitoring directly into Neovim, offering real-time updates, quick dispatch capabilities, and seamless integration with existing Neovim configurations.

Overview

See status of ci/cd pipeline runs directly in neovim. Currently supports GitHub Actions and GitLab CI.

Use Cases

Best For

Monitoring GitHub Actions pipeline status without leaving Neovim
Dispatching new CI/CD runs directly from the editor
Managing pipelines across multiple Git remotes (e.g., origin and upstream)
Integrating CI/CD status into lualine for real-time visibility
Quickly opening pipeline runs or jobs in a browser from Neovim
Reducing context switching during development and code review

Not Ideal For

Projects relying on CI/CD platforms like Jenkins, CircleCI, or Azure DevOps, as these are not supported.
Teams that need immediate ability to rerun failed pipelines or customize keybindings, features currently missing from the plugin.
Environments where installing Rust (Cargo) or yq is not practical, due to build dependencies or security restrictions.

Pros & Cons

Pros

Real-time Status Updates

Refreshes pipeline lists every 10 seconds by default, providing live monitoring without leaving the editor, as shown in the refresh_interval option.

Multi-Remote Management

Supports multiple Git remotes such as origin and upstream, allowing seamless switching between different repository sources for flexible workflow handling.

Integrated Browser Actions

Includes keybindings like 'gp' to open pipeline runs directly in a browser, reducing context switching by keeping actions within Neovim.

Extensive Customization

Offers configurable split windows, icons, highlights, and more through a detailed options table, enabling personalized UI adjustments.

Cons

Unstable GitLab Support

The README admits GitLab CI is 'fairly untested', making it potentially buggy and unreliable for production use with GitLab.

Incomplete Feature Set

Critical features like rerunning failed jobs and configurable keybindings are listed as ToDo, not yet implemented, limiting functionality.

Complex Dependencies

Requires either yq or building with GNU Make and Cargo, adding installation overhead compared to simpler, pure Lua Neovim plugins.

Frequently Asked Questions

Related Projects

octo.nvim

Edit and review GitHub issues and pull requests from the comfort of your favorite editor

Stars3,289

Forks232

Last commit6 days ago

gh.nvim

A fully featured GitHub integration for performing code reviews in Neovim.

Stars647

Forks31

Last commit1 year ago

gist.nvim

Neovim plugin that allows you to create a Github Gist from the current file

Stars215

Forks8

Last commit12 days ago

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