[Idea] Using lazy.nvim
to manage non-plugin repositories
#1724
pidgeon777
started this conversation in
Ideas
Replies: 1 comment
-
EDIT: I just found out this: I was wondering if there could be something else missing, or coming in the next future to make this a built-in "feature". |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Overview
The idea is to leverage lazy.nvim to manage repositories that are not necessarily plugins. Below is an example screenshot:
This was achieved with the following configuration:
Issues Encountered
LazyVim
, the repository reappears with the same commits as before.lazy.nvim
indicating available updates for the repository, the repository name does not appear in the notify list of available updates when starting neovim. Only updates for actual plugins are displayed.Insight
My intuition is that
lazy.nvim
already has the necessary functionality to update non-plugin repositories. However, I am unsure how to configure it properly. It would be very convenient to view new updates for a repository as if it were a plugin. Additionally, it would be possible to automatically execute certain commands likemake
or others for each update.Beta Was this translation helpful? Give feedback.
All reactions