Repository navigation
Closed
Labels
🌊 upstreamDepends on an upstream solve beyond starshipDepends on an upstream solve beyond starship🐛 bugSomething isn't working as expected.Something isn't working as expected.
Description
pkg_version:1.19.0
branch:
commit_hash:
build_time:1980-01-01 00:00:00 +00:00
build_env:rustc 1.78.0 (9b00956e5 2024-04-29) (built from a source tarball),
Current Behavior
Git 2.45 is needed to reproduce this bug, since it makes use of the new reference storage backend "reftable".
Just clone a git repository with reftable used:
git clone --ref-format=reftable [email protected]:starship/starship.gitThen go to the newly cloned directory. Git information are not displayed properly:
…/starship [🌱 HEAD](+0/-0)Expected Behavior
The bit branch and git commit should be shown:
…/starship [🌱 master](27cc4bc)(+0/-0)Environment
- Starship version: 1.19.0
- zsh version: zsh 5.9 (aarch64-apple-darwin23.5.0)
- Operating system: Mac OS 14.5.0
- Terminal emulator: Apple_Terminal 453
- Git Commit Hash:
- Branch/Tag:
- Rust Version: rustc 1.78.0 (9b00956e5 2024-04-29) (built from a source tarball)
- Rust channel: release
- Build Time: 1980-01-01 00:00:00 +00:00
Starship Configuration
[git_branch]
format = "\\[[$symbol$branch]($style)\\]"
style = "bold yellow"
symbol = "🌱 "
[git_commit]
commit_hash_length = 7
format = "[\\($hash\\)]($style)( [\\($tag\\)]($style))"
only_detached = false
style = "bold white"
tag_disabled = false
tag_symbol = "🔖"
[git_metrics]
added_style = "bold dimmed green"
deleted_style = "bold dimmed red"
disabled = false
format = "\\([+$added]($added_style)/[-$deleted]($deleted_style)\\)"
only_nonzero_diffs = false
[git_state]
format = "[\\($state( $progress_current of $progress_total)\\)]($style) "
[git_status]
ahead = "🏎💨×$count"
behind = "🐢×$count"
conflicted = "⚔"
deleted = "🗑×$count"
diverged = "🏎💨×$ahead_count 🐢×$behind_count"
format = "([\\[$all_status$ahead_behind\\]]($style))"
modified = "📝×$count"
renamed = "📛×$count"
staged = "🗃×$count"
stashed = "📦"
style = "bold white"
untracked = "🛤"Reacted by Damyan Yordanov, FirelightFlagboy, Anders Kaseorg, Maksim Bondarenkov, Dennis Theisen, Sebastian Melchior, Akkad Marano, Teppei Taguchi, Gabriel Mazzetto and Bryan Hoang
Metadata
Metadata
Assignees
Labels
🌊 upstreamDepends on an upstream solve beyond starshipDepends on an upstream solve beyond starship🐛 bugSomething isn't working as expected.Something isn't working as expected.
Activity
FirelightFlagboy commentedon Jul 6, 2025
After looking how the information is retreive on starship side, it seems that the dependency
gixdoes not supportreftable.My reasoning for that is the branch name is retrieve from:
starship/src/context.rs
Lines 832 to 834 in 76f125b
(
Repositoryis imported fromgix:starship/src/context.rs
Lines 10 to 11 in 76f125b
which is use to set the actual branch name in
get_repo:starship/src/context.rs
Line 343 in 76f125b
Which is used in the module
git_branch:starship/src/modules/git_branch.rs
Line 27 in 76f125b
It seems that they already have a tracking issue on
gixside: GitoxideLabs/gitoxide#109Soleone commentedon Nov 3, 2025
This just became very relevant at our company for many developers as we're switching to reftables for a monorepo.
jaudiger commentedon Nov 3, 2025
Starting with Git 3.0, this backend should become the default when cloning new repositories as mentioned here:
denysovkos commentedon Nov 19, 2025
Hi there 👋
I’m running into the same issue outlined here: [Git 2.51.2] Reftable storage backend is not supported #6086
When I navigate to a repo it always shows HEAD as the branch instead of the actual branch name, which is quite uncomfortable when I want to see the current branch.
Could you share any updates on this? Thanks!
git_branchmodule does not work properly inreftableenabled git repos #7101 as a duplicate of this issueakkadaya commentedon Nov 28, 2025
How can I get a notification when this is implemented? I will switch to oh-my-posh for now until it's fixed, it seems it's working on OMP
Byron commentedon Nov 28, 2025
Actually you can turn that off and resort to the Git executable, the most compatible option:
FirelightFlagboy commentedon Nov 28, 2025
Even with
use_git_executable = true, the branch is not the correct one:Starship git_status config
akkadaya commentedon Nov 28, 2025
yeah, I was going to say it's not working. It should be added/used in
git_branchnotgit_statusFirelightFlagboy commentedon Nov 28, 2025
Starship git_branch config
akkadaya commentedon Nov 28, 2025
Sorry, I edited my comment
that option should be implemented for
git_branch, maybe it's a temporary solution for nowAdd use_git_executable option to git_branch module
Add use_git_executable option to git_branch module
fix(git_branch) auto-detect reftable usage and fallback to Git exectu…
fix(git_branch) auto-detect reftable usage and fallback to Git exectu…