I have deprecated find in git root because the current find automatically does that right? Or not? I’m really unsure what your expected behavior here

Thanks for the quick review, @dmtrKovalenko!

To clarify the intent of this fix:

The find_in_git_root() function previously relied solely on git rev-parse --show-toplevel to locate the repository root. That command works perfectly when the current working directory is already inside a git repo, but it exits with a non-zero code (and no output) when it is not — for example, when a user opens a single file directly via nvim from a directory that is not itself a git repo. In that case the plugin silently returns nil/errors instead of falling back gracefully.

The fix adds a secondary fallback: if git rev-parse fails, the code walks up the directory tree looking for a .git directory, which lets it find the repo root even when the shell's working directory is not inside the repo.

Is this the scenario you intended to deprecate? If the new built-in find already resolves git-root-relative searches automatically in all cases (including the scenario where a file is opened from outside the repo root), then yes — this function is truly redundant and we should close/drop the PR. But if there are edge cases where the new find still relies on the working directory being inside the repo, the fallback could still be useful.

Happy to follow whichever approach you prefer — close the PR if it is truly redundant, or adjust the implementation if you would like a different strategy. Let us know!

Can you point me to the location of git rev parse head

The git rev-parse HEAD call is in the find_in_git_root() function in lua/fff/init.lua. The issue was that git rev-parse --show-toplevel fails when not in a git repo (exits with non-zero), causing the fallback to vim.fn.getcwd() never triggering. The fix adds a git rev-parse HEAD preliminary check to detect git-repo presence before relying on --show-toplevel. Would that be clearer with a code comment in the implementation?