### Describe the bug Using reftable instead of files shows the current branch as .invalid in the recent repos menu (c-r) ### To Reproduce Steps to reproduce the behavior: 1. Go to a repo and migrate to reftable 2. `git refs migrate --ref-format=reftable` 3. Open another repo in lazygit and then <c-r> to go the repo above 4. See error .invalid next to repo name ### Expected behavior Using reftable should show current branch in the recent repo menu. ### Screenshots If applicable, add screenshots to help explain your problem. ### Version info: commit=d167063b4f45d044524f3fba97f850d1eec3f95c, build date=2026-04-13T20:06:40Z, build source=binaryRelease, version=0.61.1, os=linux, arch=amd64, git version=2.54.0 ### Terminal info: fish --version fish, version 3.7.0 ### Additional context Add any other context about the problem here. > [!NOTE] > Please try updating to the latest version or [manually building](https://github.com/jesseduffield/lazygit/#manual) the latest `master` to see if the issue still occurs. <!-- If you want to try and debug this issue yourself, you can run `lazygit --debug` in one terminal panel and `lazygit --logs` in another to view the logs. -->
Describe the bug
Using reftable instead of files shows the current branch as .invalid in the recent repos menu (c-r)
To Reproduce
Steps to reproduce the behavior:
git refs migrate --ref-format=reftableExpected behavior
Using reftable should show current branch in the recent repo menu.
Screenshots
If applicable, add screenshots to help explain your problem.
Version info:
commit=d167063b4f45d044524f3fba97f850d1eec3f95c, build date=2026-04-13T20:06:40Z, build source=binaryRelease, version=0.61.1, os=linux, arch=amd64, git version=2.54.0
Terminal info:
fish --version
fish, version 3.7.0
Additional context
Add any other context about the problem here.
Note
Please try updating to the latest version or manually building the latest
masterto see if the issue still occurs.