Skip to content

feature: optional merge instead of hard reset for updates #2175

Description

@Universal-Invariant

Did you check the docs?

  • I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.

I've modified files to make plugin work. e.g. nvim.yazi uses absolute paths which fail under my system. I changed them to relative paths and it works. nvim.mason has some issues with go since it is hard coded to use go. rather than go.exe and has issues when it gets the version information. I changed those in the local mason repo so mason passes the go.exe health checks.

But then lazy.nvim cannot update because the local repo has changed. Any forced updating will destroy the changes. Manually having to update the plugins defeats the entire point. Using a fork defeats the point of automated updates.

Describe the solution you'd like

I can pin but then I lose the ability to update automatically. We should have an option to be able to do a merge update or, even a custom command to update. E.g., I could put my changes in different repo and then pull them in after a hard reset. Then any time the upstream version changes lazynvim will update them.

Describe alternatives you've considered

There are no alternatives except either manually updating specific plugins that must be modified locally to get to work or try to push the changes to remote and hope they will accept and update them in due time.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions