You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I dont really like to update all plugins in one swoop, too much chance of breakage. However when I dont update for a while there is a very big chance there is a lot of plugins that need to be updated which is annoying to go through manually. OTOH a lot of small stable plugins have "updates" that are just tweaks to the docs, ci, etc. If i see a changelog full of dimmed commits I can probably just hit update, which makes the text of the plugins page jump around, disrupting my reading of other plugins changelogs.
Describe the solution you'd like
Plugins with only easily ignorable dimmed commits in the changelog could be:
shown in a separate section
all updated with one keypress
maybe even just autoupdated on startup (if we assume that plugin authors actually properly tag their commits and dont put anything significant in these prefixes:
Did you check the docs?
Is your feature request related to a problem? Please describe.
I dont really like to update all plugins in one swoop, too much chance of breakage. However when I dont update for a while there is a very big chance there is a lot of plugins that need to be updated which is annoying to go through manually. OTOH a lot of small stable plugins have "updates" that are just tweaks to the docs, ci, etc. If i see a changelog full of dimmed commits I can probably just hit update, which makes the text of the plugins page jump around, disrupting my reading of other plugins changelogs.
Describe the solution you'd like
Plugins with only easily ignorable dimmed commits in the changelog could be:
lazy.nvim/lua/lazy/view/config.lua
Line 27 in 1159bdc
Perhaps the set of trivial/ignorable commit prefixes could be user configurable
Describe alternatives you've considered
Just keep on trucking and manually updating these trivial updates
Additional context
No response
The text was updated successfully, but these errors were encountered: