Repository navigation
fix(filters): include repos with a dirty worktree in the Dirty filter - #71
Merged
Merged
Conversation
rocketraman
force-pushed
the
claude/dirty-filter-worktree-315b66
branch
from
October 23, 2026 02:10
9650d70 to
53c67d3
Compare
The Dirty filter only looked at a repo's own checkout, so a repo whose main checkout was clean but whose linked worktree held uncommitted changes never showed up. The filter and its chip count now use RepoView.dirtyAnywhere, which also checks the linked worktrees. isDirty is unchanged: it still drives the row's badges and Commit button, which act on the main checkout only. Signed-off-by: Raman Gupta <rocketraman@gmail.com>
rocketraman
force-pushed
the
claude/dirty-filter-worktree-315b66
branch
from
October 23, 2026 02:11
53c67d3 to
dbda036
Compare
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
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.
What changed
The Dirty status filter, and the number on its chip, now include a repo when any of its linked worktrees has uncommitted changes, even if the main checkout is clean.
RepoView.dirtyAnywhere(Derive.kt): true when the checkout itself or any linked worktree has uncommitted changes.AppState.counts()andstatusPredicateuse it for"dirty".DirtyFilterTestcovers: a clean checkout with a dirty worktree, a dirty checkout, everything clean, and a snoozed dirty worktree.Why
Before this change, a repo was hidden from Dirty whenever its main checkout was clean, even if a worktree held uncommitted work.
For reviewers
isDirtyhasn't changed. It still drives the row's "modified" badges and the Commit button, and both only act on the main checkout. So a repo that's only dirty in a worktree appears under Dirty but has no Commit button.isDirty: a snoozed worktree with changes still counts.