rhysd / rhysd/action-setup-vim

Build specific commit for nvim nightly

Open
#68 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
166
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Hi!

I maintain some neovim plugins and run some end-to-end tests in my github actions runs to try to make them easier to maintain. For this purpose, I try to be very strict about the neovim versions (both releases and nightly commits), so that the test runs are more reproducible. With many dependencies, the dependencies drifting can make maintenance a headache. 🙂

I recently implemented support in one of my projects for building+caching neovim's nightly version at a specific commit id (see the setup-neovim-nightly and download-neovim-nightly actions).

I was wondering if there is any interest to upstream this functionality to this action.

I took a quick look at the current implementation in this action, and it looks like the major differences are:

  1. the latest neovim commit is always used, not possible to configure which commit to build
  2. It looked like there is no caching. Perhaps the common case is to download the prebuilt nightly so there is no need to do it.

Not sure how well this would fit but figured it could be good to throw some ideas around at least 🙂

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the current action implementation and the linked setup-neovim-nightly and download-neovim-nightly action.yml files. Determine how a commit can be configured and how nightly artifacts can be cached across the supported platforms; done means the action can build and cache the requested commit reproducibly.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.