bug: changing plugin author name doesn't re-pull the repo

[Avishayy]

Did you check docs and existing issues?

• I have read all the lazy.nvim docs
• I have searched the existing issues of lazy.nvim
• I have searched the exsiting issues of plugins related to this issue

Neovim version (nvim -v)

v0.8.1 brew@Ventura

Operating system/version

macOS Ventura 13.1

Describe the bug

I was forking a plugin to add a feature. Rather than adding the dev config I was lazy so I changed the author name in the plugin file and tried to update, but to no avail.

From this:

-- lua/plugins/treesiter.lua
return {
  {
    "nvim-treesitter/nvim-treesitter-context",
    event = "BufReadPre",
    config = true,
  },
 -- ...
}

to this:

-- lua/plugins/treesiter.lua
return {
  {
    -- can also set any giberrish author name, it doesn't matter
    "avishayy/nvim-treesitter-context",
    event = "BufReadPre",
    config = true,
  },
 -- ...
}

Lazy won't pick up on the fact that the plugin is now changed (update / build do nothing different, they use the cached repo). I worked around it by deleting the plugin lines, deleting the plugin with Lazy and then adding the lines with the new author.

Steps To Reproduce

1. Change author in repo path to anything you'd like
2. Try to update
3. Nothing changes

Expected Behavior

Actual update, if new author has repo, pull and build it. If new author doesn't exist, an error as usual.

Repro

I don't know how to provide a repro for the manual renaming part, sorry. (But I did provide the relevant code bits in the description)

[folke]

That is correct. A plugin dir is not based on the author name. You can remove the plugin and re-install it from the ui with <x> and <i>`. I won't add any special handling for this.

[folke]

I've now added functionality that detects origin changes and will fix it during an update.

[Avishayy]

Cool, thank you!