Back to Signal Feed
CodeTracked since May 20, 2026

Fix commit message targeting for multi-root workspaces

The key change fixes commit message generation in multi-root workspaces by ensuring commit operations resolve the active repository at action time instead of using a globally cached first root, so messages are generated for the repo the developer is actually working in.

multi-root workspacecommit message generationCommitServiceSourceControl rootUri

What Happened

  • The key change fixes commit message generation in multi-root workspaces by ensuring commit operations resolve the active repository at action time instead of using a globally cached first root, so messages are generated for the repo the developer is actually working in.
  • The key change fixes commit message generation in multi-root workspaces by ensuring commit operations resolve the active repository at action time instead of using a globally cached first root, so messages are generated for the repo the developer is actually working in.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced per-action workspace-root resolution for commit message generation: removed the singleton CommitService root cache and passed the active SourceControl root URI as a workspaceRootHint so commit workflows can consistently bind to the correct repository in multi-repo sessions.

Why Track This

Why It Matters

Developers working in VS Code with multiple repositories open can now generate commit messages for the currently active project instead of accidentally targeting another repo, which reduces misfiled review metadata and broken workflow handoffs; teams should still watch mixed-repo edge cases where root detection might still resolve incorrectly after rapid workspace switching. The fix replaces a singleton cached root path in the commit service with active root hints from SourceControl, directly addressing cross-repo ambiguity in multi-root environments and making generated commit context more reliable.

Impact

Developers working in VS Code with multiple repositories open can now generate commit messages for the currently active project instead of accidentally targeting another repo, which reduces misfiled review metadata and broken workflow handoffs; teams should still watch mixed-repo edge cases where root detection might still resolve incorrectly after rapid workspace switching. The fix replaces a singleton cached root path in the commit service with active root hints from SourceControl, directly addressing cross-repo ambiguity in multi-root environments and making generated commit context more reliable.

What To Watch Next

  • Watch whether multi-root workspace becomes a repeated pattern.
  • Track follow-up changes around AI Code Review.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: monitor_root_resolution_after_workspace_switches, watch_for_other_services_relying_on_singleton_root_cache.
Open Topic TimelineOpen Technical EventOpen Original Sourcemonitor_root_resolution_after_workspace_switches / watch_for_other_services_relying_on_singleton_root_cache / verify_nested_workspace_path_edge_cases

Supporting Evidence

GITHUB COMMIT BURSTHigh Trust

zgsm-ai/costrict commit burst: 4 commits in 7 days

Support commit message generation in multi-root workspaces by removing cached singleton root usage and passing rootUri as workspaceRootHint.