fix(git): treat selected commit paths literally

[EricTsai83]

What Changed

• Pass Git's global --literal-pathspecs option when staging explicitly selected files.
• Add regression coverage for selected filenames containing Git pathspec metacharacters.

Why

Selected paths come from UI file selections and represent concrete filenames.

Without literal pathspec handling, Git interprets metacharacters in a filename as pathspec syntax. For example, selecting selected[1].txt can stage selected1.txt instead.

The existing -- separator prevents paths from being parsed as command options, but it does not disable Git pathspec expansion.

This keeps Git's normal pathspec behavior unchanged elsewhere and applies literal handling only at the exact-file selection boundary.

Testing

• vp test run apps/server/src/vcs/GitVcsDriverCore.test.ts — passed (25 tests)
• vp check — passed
• vp run typecheck — passed
• vp run test — attempted; desktop suites could not load because Electron is not installed correctly in the local environment (Electron failed to install correctly)

Checklist

• This PR is small and focused
• I explained what changed and why
• No UI changes
• No animation or interaction changes

---

Note

Low Risk
Narrow change at the selected-file staging boundary with a targeted test; no auth, UI, or broad git behavior changes.

Overview
Partial commits from UI file selections now stage exact paths instead of letting Git treat brackets and other metacharacters as pathspec globs.

prepareCommitContext adds --literal-pathspecs to the git add call when filePaths is non-empty, so a selection like selected[1].txt no longer also picks up selected1.txt. Staging everything (add -A with no path list) is unchanged.

A regression test covers the bracket-in-filename case.

^{Reviewed by Cursor Bugbot for commit 5fb91ea. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix prepareCommitContext to treat selected file paths as literal pathspecs

Adds --literal-pathspecs to the git add invocation in GitVcsDriverCore.ts when staging specific files, preventing git from interpreting special characters (e.g. brackets) as glob patterns. A test verifies that a file named selected[1].txt is staged without also matching selected1.txt.

^{Macroscope summarized 5fb91ea.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9ba75fe6-1fed-4824-a66a-3f028c0eda0f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved

Straightforward bug fix adding git's --literal-pathspecs flag to prevent file paths with special characters (e.g., [1]) from being interpreted as glob patterns. Single line change with comprehensive test coverage.

^{You can customize Macroscope's approvability policy. Learn more.}