Skip to content

spec: refresh repo metadata after claude --worktree (#10031)#10230

Open
lonexreb wants to merge 1 commit intowarpdotdev:masterfrom
lonexreb:spec/10031-claude-worktree-metadata
Open

spec: refresh repo metadata after claude --worktree (#10031)#10230
lonexreb wants to merge 1 commit intowarpdotdev:masterfrom
lonexreb:spec/10031-claude-worktree-metadata

Conversation

@lonexreb
Copy link
Copy Markdown
Contributor

@lonexreb lonexreb commented May 6, 2026

Spec for #10031. CWD-tracking hook gains a 'repo-root changed' signal driven by (toplevel, git-common-dir) tuple change. Existing repo-metadata subsystem refreshes on event. Throttled to 2/sec/pane. Clears metadata when CWD leaves a git repo.

Closes (spec-only) #10031.

@cla-bot cla-bot Bot added the cla-signed label May 6, 2026
@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 6, 2026

@lonexreb

I'm starting a first review of this spec-only pull request.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@github-actions github-actions Bot added the external-contributor Indicates that a PR has been opened by someone outside the Warp team. label May 6, 2026
Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This spec defines a CWD-driven repo context refresh for git worktree/repo transitions and metadata clearing when a pane leaves a git repo.

Concerns

  • The throttle acceptance criterion conflicts with the behavior contract if top-level and git-common-dir are derived with separate git rev-parse invocations.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Comment thread specs/GH10031/SPEC.md
Comment on lines +52 to +53
- A5. Throttle: rapid back-and-forth `cd` does not spawn more
than 2 `git rev-parse` per second.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [IMPORTANT] B1/B3 can produce up to two git rev-parse commands per derivation, so this limit is internally inconsistent with a 500ms throttle unless both values come from one process. Specify the intended budget in commands vs derivations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed external-contributor Indicates that a PR has been opened by someone outside the Warp team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant