mhinz / mhinz/vim-signify

New release

Open
#378 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Vim Script
Stars
2.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

That probably sounds old school but contrary to 99% of vim users I prefer to manage installed vim plugins just like any other software/plugins on my system -- through package manager. Official releases help a lot in doing so :) Is there any chance for a new tag/release or is "checkout git branch through vim package manager which you checked out from git branch" the only model maintained by vim-signify?

Contributor guide

Open the contributing guide

Research direction

The issue names no file or test. First review the project's existing release and tag history, then check how Vim package managers consume official releases. Done means deciding whether a new release is supported and, if so, publishing a tag that package managers can use.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.