Skip to content

Add developer worktree tools for parallel development workflows#445

Merged
harrism merged 2 commits into
openvdb:mainfrom
harrism:devtools/worktree-scripts
Feb 11, 2026
Merged

Add developer worktree tools for parallel development workflows#445
harrism merged 2 commits into
openvdb:mainfrom
harrism:devtools/worktree-scripts

Conversation

@harrism

@harrism harrism commented Feb 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds devtools/worktree/ directory with scripts for managing Git worktrees across fvdb-core and fvdb-reality-capture
  • fvdb-open: Interactive launcher for opening worktrees in Cursor
  • fvdb-issue: Creates worktrees for GitHub issues with AI agent context
  • fvdb-close: Safely removes worktrees with branch cleanup
  • Includes install.sh for easy setup and comprehensive README documentation

These tools enable parallel development workflows where multiple AI agents (or developers) can work on different issues simultaneously in separate worktrees.

Test plan

  • Tested install.sh - creates config file and installs scripts to ~/bin
  • Tested fvdb-open - interactive worktree selection and Cursor launch
  • Tested fvdb-issue - issue fetching, worktree creation, context file generation
  • Tested fvdb-close - worktree listing and removal with branch deletion prompt

Made with Cursor

@harrism harrism requested a review from a team as a code owner February 6, 2026 05:50
Adds fvdb-open, fvdb-issue, and fvdb-close scripts that enable:
- Managing Git worktrees across fvdb-core and fvdb-reality-capture
- Creating worktrees for GitHub issues with AI agent context
- Running multiple AI agents on different issues in parallel

Includes install.sh for easy setup and comprehensive README documentation.

Signed-off-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@harrism harrism force-pushed the devtools/worktree-scripts branch from d5febb6 to 74f64fc Compare February 6, 2026 05:53
@harrism harrism added the new feature New feature or request label Feb 6, 2026
@harrism harrism added this to fVDB Feb 6, 2026
@harrism harrism requested a review from Copilot February 10, 2026 03:59

Copilot AI left a comment

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.

Pull request overview

Adds a small suite of local developer scripts to manage Git worktrees across fvdb-core and fvdb-reality-capture, aimed at enabling parallel (multi-branch / multi-agent) workflows.

Changes:

  • Introduces devtools/worktree/ with fvdb-open, fvdb-issue, fvdb-close, an install.sh, and documentation.
  • Updates .gitignore to ignore worktree-specific Cursor agent rule files.
  • Adjusts repo VS Code settings by commenting out C++/CUDA formatter-on-save blocks.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 13 comments.

Show a summary per file
File Description
devtools/worktree/install.sh Installer/uninstaller for the worktree helper scripts plus config bootstrap.
devtools/worktree/fvdb-open Interactive/direct worktree selector and Cursor multi-root launcher.
devtools/worktree/fvdb-issue Creates issue-based worktrees using gh/jq, generates agent context, launches Cursor/Claude.
devtools/worktree/fvdb-close Interactive/direct worktree removal with optional branch cleanup.
devtools/worktree/README.md User docs for installation, usage, and workflow examples.
.vscode/settings.json Comments out C++/CUDA format-on-save settings.
.gitignore Ignores .cursor/rules/ directory.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .vscode/settings.json Outdated
Comment thread devtools/worktree/fvdb-issue
Comment thread devtools/worktree/fvdb-open Outdated
Comment thread devtools/worktree/install.sh Outdated
Comment thread devtools/worktree/fvdb-close Outdated
Comment thread devtools/worktree/fvdb-open
Comment thread devtools/worktree/fvdb-issue Outdated
Comment thread devtools/worktree/fvdb-open Outdated
Comment thread devtools/worktree/fvdb-close Outdated
Comment thread devtools/worktree/fvdb-issue
- Revert accidental .vscode/settings.json change
- Centralize branch-to-worktree-path normalization in fvdb-open
- Parse branch names from [brackets] instead of second column in worktree list
- Check for editor command availability with FVDB_EDITOR_CMD override
- Add early dependency checks (gh, jq, fvdb-open) in fvdb-issue
- Derive default branch via symbolic-ref instead of hardcoding origin/main
- Replace ${var,,} with tr for Bash 3.2 compatibility
- Use grep -F for safe path matching in fvdb-close
- Try worktree remove without --force first, offer force on failure
- Add macOS lsof fallback for in-use detection
- Detect active shell via $SHELL in install.sh
- Document Bash 4+, Linux /proc, claude CLI in README requirements

Signed-off-by: Mark Harris <mharris@nvidia.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

@blackencino blackencino left a comment

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.

Because this workflow is not replacing something, and represents a methodology that you've come up with and are using already, we should try it out before requesting changes. Since you've already addressed the copilot suggestions, I think this is great and we should give it a go.

LGTM!

@harrism harrism merged commit 9b0b69d into openvdb:main Feb 11, 2026
32 checks passed
@github-project-automation github-project-automation Bot moved this to Done in fVDB Feb 11, 2026
@harrism harrism deleted the devtools/worktree-scripts branch February 11, 2026 00:15
@swahtz swahtz assigned swahtz and unassigned swahtz Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new feature New feature or request

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants