Chore: rename fff.nvim repo refs - #762
Merged
dmtrKovalenko merged 2 commits intoAug 12, 2026
Merged
Conversation
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.
dmtrKovalenko
approved these changes
Aug 12, 2026
abhijit-s
pushed a commit
to abhijit-s/fff
that referenced
this pull request
Aug 13, 2026
Brings in upstream fixes on top of our 0.18.0 fork: - fix(grep) dmtrKovalenko#756/dmtrKovalenko#764: literal/regex fallback now keeps an explicit FilePath scope so a top-level regex alternation can't leak matches outside the pinned path - fix dmtrKovalenko#754/dmtrKovalenko#765: missing clap attribute on no_content_indexing - fix(bun) dmtrKovalenko#766: proper build step for fff-bun - chore dmtrKovalenko#762: rename stale fff.nvim repo refs to fff Conflicts resolved preserving fork divergences: - update_check.rs / install-mcp.sh: kept our DEFAULT_REPO=abhijit-s/fff and FFF_UPDATE_REPO override; upstream's fff.nvim->fff rename does not apply since we target our own fork for update checks and installs - README.md: kept our rewritten Homebrew-tap/apt/fffctl install section; upstream only tweaked a release URL in a block our fork already removed - grep_tests.rs: add/add at EOF resolved as a union — kept our three cold-start readiness tests and adopted upstream's dmtrKovalenko#756 regex-scope test, reflowing the shared trailing braces so both functions close correctly grep.rs auto-merged; reviewed the dmtrKovalenko#756 fallback change against our surrounding fork logic and confirmed coherence. Makefile .PHONY targets and the per-root ignore feature (ignore.rs/main.rs) preserved; workspace stays at 0.18.0. Build green (fff-mcp/fff-engine/fff-ctl); fff-search + fff-engine tests 375 passed, 0 failed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I found while installing from the repo docs that several references use the outdated
github.com/dmtrKovalenko/fff.nvimrepo 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
dmtrKovalenko/fff.nvimrepository URLs todmtrKovalenko/fffafter the GitHub repo rename (download.lua, MCP installers, Homebrew formula, docs, package metadata).fff.nvimto minimize upgrade pain for existing nvim users that update their config from the docs.fffwith 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
pname/health fromfff.nvimtofff?