无法开启存档点

[hem951740-max]

Problem (one or two sentences)

开启存档点后提示：存档点已禁用，因为在 UniHospReview-java-be 检测到嵌套的 git 仓库。要使用存档点，请移除或重新定位此嵌套的 git 仓库。但是我自己的代码也需要进行版本控制，我不可能删除我自己的.git文件

Context (who is affected and when)

开启存档点后提示：存档点已禁用，因为在 UniHospReview-java-be 检测到嵌套的 git 仓库。要使用存档点，请移除或重新定位此嵌套的 git 仓库。但是我自己的代码也需要进行版本控制，我不可能删除我自己的.git文件

Reproduction steps

开启存档点后提示：存档点已禁用，因为在 UniHospReview-java-be 检测到嵌套的 git 仓库。要使用存档点，请移除或重新定位此嵌套的 git 仓库。但是我自己的代码也需要进行版本控制，我不可能删除我自己的.git文件

Expected result

开启存档点后提示：存档点已禁用，因为在 UniHospReview-java-be 检测到嵌套的 git 仓库。要使用存档点，请移除或重新定位此嵌套的 git 仓库。但是我自己的代码也需要进行版本控制，我不可能删除我自己的.git文件

Actual result

开启存档点后提示：存档点已禁用，因为在 UniHospReview-java-be 检测到嵌套的 git 仓库。要使用存档点，请移除或重新定位此嵌套的 git 仓库。但是我自己的代码也需要进行版本控制，我不可能删除我自己的.git文件

Variations tried (optional)

No response

App Version

v3.36.7

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'd like to help with this issue. To better understand your situation and propose the right solution, could you please provide some clarification?

Questions (请回答以下问题):

1. What folder did you open in VS Code? Is it a parent directory that contains "UniHospReview-java-be" as a subdirectory, or is "UniHospReview-java-be" the folder you opened directly?

   (您在 VS Code 中打开的是哪个文件夹？是包含 "UniHospReview-java-be" 作为子目录的父目录，还是直接打开了 "UniHospReview-java-be" 文件夹？)

2. Is your project structure like this? (您的项目结构是这样吗？)

   parent-folder/           <- Did you open this folder?
   └── UniHospReview-java-be/
       └── .git/           <- Your project's git repository
   

   Or like this? (还是这样？)

   UniHospReview-java-be/   <- Did you open this folder?
   └── .git/               <- Your project's git repository
   └── some-submodule/
       └── .git/           <- Nested git repository
   

The checkpoint feature detects nested git repositories to prevent conflicts. If you opened a parent directory containing your project, you can try opening the project folder directly (UniHospReview-java-be) in VS Code, and the checkpoints should work.

Please tag @roomote in your response with more details about your setup, and I'll be happy to help resolve this or propose a code change if needed.

[hem951740-max]

我项目是前后端分离的项目，前后端分别有各自的git文件，但是我使用vscode打开的是前后端的文件的共同父文件夹方便ai进行查找，如果分开打开的话，无法找到文件

[hem951740-max]

@roomote 这种情况下，应该如何开启存档点

[roomote]

I've seen your comment and understand the issue. Your situation is a valid use case - working with a parent folder containing multiple sibling projects (frontend and backend), each with their own git repositories.

Current Behavior:
The checkpoint feature currently blocks initialization when it detects any nested .git directories, even when the parent folder itself has no .git.

Proposed Fix:
I'll modify the checkpoint service to allow checkpoints when the workspace root does NOT have its own .git folder. In this case:

1. The shadow repository can safely create its own version control
2. Subdirectory .git folders are already excluded from tracking via exclude patterns
3. There's no conflict with your project's version control since each project manages its own git independently

I'll open a PR with this fix shortly.

---

我已经看到您的评论并理解了这个问题。您的使用场景是合理的 - 在一个父文件夹中包含多个子项目（前端和后端），每个子项目都有自己的 git 仓库。

当前行为:
存档点功能目前在检测到任何嵌套的 .git 目录时都会阻止初始化，即使父文件夹本身没有 .git。

建议的修复:
我将修改存档点服务，在工作区根目录没有自己的 .git 文件夹时允许存档点功能。在这种情况下：

1. 影子仓库可以安全地创建自己的版本控制
2. 子目录的 .git 文件夹已通过排除模式被排除在跟踪范围外
3. 与您项目的版本控制不会冲突，因为每个项目独立管理自己的 git

我将很快打开一个 PR 来修复这个问题。

[roomote]

Opened a PR with my attempt at addressing this: #10130

The fix allows checkpoints to work when the workspace root has no .git directory but subdirectories have their own git repositories. This should enable your use case of opening a parent folder containing both frontend and backend projects.

Feedback welcome!

---

我已经提交了一个修复此问题的 PR: #10130

此修复允许在工作区根目录没有 .git 目录但子目录有各自的 git 仓库时启用存档点功能。这应该能够支持您打开包含前端和后端项目的父文件夹的使用场景。

欢迎反馈！

[hannesrudolph]

Apologies for the delayed response.

Bug report is missing the minimum information we need to triage.

Please open a new issue (and link back to this one) and fill out the form with:

• Concrete repro steps (numbered) starting from a clean workspace
• Expected vs actual (include the exact full error text)
• Versions: Roo Code v3.36.7, VS Code version, OS
• Your repo layout relevant to the error:
  • which folder you opened in VS Code
  • the path to the workspace root .git
  • the path to the nested .git Roo is detecting
  • whether that nested repo is a git submodule, subtree, or a standalone repo checked out inside the parent
• Roo Code Task Links (if applicable)

We are not going to continue iterating in this thread. A new issue with the completed form is required.