gitbutlerapp/gitbutler

`but branch list|show` use their own version of a persisted CliId mapping

Open

#11,276 opened on Nov 18, 2025

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Rust (862 forks)batch import
help wanted

Repository metrics

Stars
 (19,787 stars)
PR merge metrics
 (Avg merge 14h 43m) (446 merged PRs in 30d)

Description

What it does is to just assign a number to each of them, and each time but branch list is run, it stores a mapping from CliId to branch name in .git/gitbutler/branch_id_map.json.

This isn't what we want, as we really don't want to create more loose files. Nor is the idea of CliIds that they must be persisted to work.

These commands should be cleaned up to use a standard CliId that can be generated from context, so persistence can be completely removed. See load_id_map and store_id_map for reference.

Contributor guide

Research direction
Examine the current implementation of CliId generation and persistence in the branch list/show commands. Understand how load id map and store id map work, then design a context based CliId that eliminates the need for persistence. Focus on the gitbutler CLI codebase, particularly the branch commands.
Tech stack
rust
Domain
clitooling
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40