Skip to content

Chore: rename fff.nvim repo refs - #762

Open
infogulch wants to merge 2 commits into
dmtrKovalenko:mainfrom
infogulch:chore/rename-fff-nvim-repo-refs
Open

Chore: rename fff.nvim repo refs#762
infogulch wants to merge 2 commits into
dmtrKovalenko:mainfrom
infogulch:chore/rename-fff-nvim-repo-refs

Conversation

@infogulch

Copy link
Copy Markdown

I found while installing from the repo docs that several references use the outdated github.com/dmtrKovalenko/fff.nvim repo name. The 301 redirect prevented this from causing an error during install but it was confusing.

This change updates docs and metadata files to use the new name.

Summary

  • Update residual dmtrKovalenko/fff.nvim repository URLs to dmtrKovalenko/fff after the GitHub repo rename (download.lua, MCP installers, Homebrew formula, docs, package metadata).
  • Keep Neovim product identity where it is still valid (help tags, health, flake pname, frontend label)
  • Two commits:
  1. New URLs + preserve package name fff.nvim to minimize upgrade pain for existing nvim users that update their config from the docs.
  2. Optional docs cleanup so package name aligns with repo basename fff with a comment for migrating users. This may cause some issues for nvim users that update their config from the docs, so this is split into a separate commit that can be dropped if desired.

Questions

  1. Accept both commits, or just commit 1?
  2. Also rename help/pname/health from fff.nvim to fff?

Update install URLs, download targets, and docs after the GitHub
rename from fff.nvim to fff. Preserve the existing Neovim package
name (fff.nvim) in lazy/vim.pack snippets so upgraders keep the same
install dir and lockfile identity.
Drop the explicit fff.nvim package name so lazy/vim.pack use fff from
the repository URL. Mild migration cost for existing installs (new
plugin dir + clean of the old one). Drop this commit to keep the
lowest-pain name=fff.nvim install snippets from the previous commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant