App Version
3.17
API Provider
Google Gemini
Model Used
gemini 2.5
🔁 Steps to Reproduce
Step 1: Add latest roocode (v3.17) extension with VSCode.
Step 2: Add API provider.
Step 3: Check if the checkpoint feature is enabled by default. If not, enable it.
Step 4: Integrate git in this solution.
Step 5: Create a file using Boomerang mode.
Step 6: Try moving the create file into git.
Result: This works fine when trying to move to git.
Step 7: Next, try restoring this file using a checkpoint. (Works well with file restore)
Step 8: After that, the git commit will not allow this file to be reverted.
Result: Git commit error: "Fatal: bad object head"
Reason for the issue: (I checked the git log for this). Its works well when creating and updating files in the checkpoint with git. But it doesn't work like that when restoring (reverting).
I'm mentioning the git log below for your understanding.
0000000000000000000000000000000000000000 a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 abdulmunafirp <abdulmunafirp@panapps.co> 1747395252 +0530 clone: from ssh://git@gitlab.panapps.co:6969/panerp-9-dev/scaffolding.git a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 d384f3a9cdd1f53499f471a8fbe20ac3072539b1 abdulmunafirp <abdulmunafirp@panapps.co> 1747395268 +0530 checkout: moving from main to RooCode d384f3a9cdd1f53499f471a8fbe20ac3072539b1 f5e0a06f93c63678cbdbc966c2196b9332a0bf0f abdulmunafirp <abdulmunafirp@panapps.co> 1747395288 +0530 commit: Admin f5e0a06f93c63678cbdbc966c2196b9332a0bf0f 343352230936e4015f1ff7a06da1f8958f7ff008 abdulmunafirp <abdulmunafirp@panapps.co> 1747395793 +0530 commit: comit 343352230936e4015f1ff7a06da1f8958f7ff008 19a76185bb084e60a29e03f16596754074a111fe Roo Code <noreply@example.com> 1747395866 +0530 reset: moving to 19a76185bb084e60a29e03f16596754074a111fe
What I understood from this, My user abdulmunafirp@panapps.co is working fine when creating and updating file using checkpoints. But when revert a file, it uses noreply@example.com. This comes from RooCode.
I hope this is looked into and resolved.
💥 Outcome Summary (Optional)
No response
📄 Relevant Logs or Errors
0000000000000000000000000000000000000000 a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 abdulmunafirp <abdulmunafirp@panapps.co> 1747395252 +0530 clone: from ssh://git@gitlab.panapps.co:6969/panerp-9-dev/scaffolding.git a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 d384f3a9cdd1f53499f471a8fbe20ac3072539b1 abdulmunafirp <abdulmunafirp@panapps.co> 1747395268 +0530 checkout: moving from main to RooCode d384f3a9cdd1f53499f471a8fbe20ac3072539b1 f5e0a06f93c63678cbdbc966c2196b9332a0bf0f abdulmunafirp <abdulmunafirp@panapps.co> 1747395288 +0530 commit: Admin f5e0a06f93c63678cbdbc966c2196b9332a0bf0f 343352230936e4015f1ff7a06da1f8958f7ff008 abdulmunafirp <abdulmunafirp@panapps.co> 1747395793 +0530 commit: comit 343352230936e4015f1ff7a06da1f8958f7ff008 19a76185bb084e60a29e03f16596754074a111fe Roo Code <noreply@example.com> 1747395866 +0530 reset: moving to 19a76185bb084e60a29e03f16596754074a111fe
App Version
3.17
API Provider
Google Gemini
Model Used
gemini 2.5
🔁 Steps to Reproduce
Step 1: Add latest roocode (v3.17) extension with VSCode.
Step 2: Add API provider.
Step 3: Check if the checkpoint feature is enabled by default. If not, enable it.
Step 4: Integrate git in this solution.
Step 5: Create a file using Boomerang mode.
Step 6: Try moving the create file into git.
Result: This works fine when trying to move to git.
Step 7: Next, try restoring this file using a checkpoint. (Works well with file restore)
Step 8: After that, the git commit will not allow this file to be reverted.
Result: Git commit error: "Fatal: bad object head"
Reason for the issue: (I checked the git log for this). Its works well when creating and updating files in the checkpoint with git. But it doesn't work like that when restoring (reverting).
I'm mentioning the git log below for your understanding.
0000000000000000000000000000000000000000 a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 abdulmunafirp <abdulmunafirp@panapps.co> 1747395252 +0530 clone: from ssh://git@gitlab.panapps.co:6969/panerp-9-dev/scaffolding.git a53ff97f04350c30ad2dd4dfa1d54c0a84220ce8 d384f3a9cdd1f53499f471a8fbe20ac3072539b1 abdulmunafirp <abdulmunafirp@panapps.co> 1747395268 +0530 checkout: moving from main to RooCode d384f3a9cdd1f53499f471a8fbe20ac3072539b1 f5e0a06f93c63678cbdbc966c2196b9332a0bf0f abdulmunafirp <abdulmunafirp@panapps.co> 1747395288 +0530 commit: Admin f5e0a06f93c63678cbdbc966c2196b9332a0bf0f 343352230936e4015f1ff7a06da1f8958f7ff008 abdulmunafirp <abdulmunafirp@panapps.co> 1747395793 +0530 commit: comit 343352230936e4015f1ff7a06da1f8958f7ff008 19a76185bb084e60a29e03f16596754074a111fe Roo Code <noreply@example.com> 1747395866 +0530 reset: moving to 19a76185bb084e60a29e03f16596754074a111feWhat I understood from this, My user abdulmunafirp@panapps.co is working fine when creating and updating file using checkpoints. But when revert a file, it uses noreply@example.com. This comes from RooCode.
I hope this is looked into and resolved.
💥 Outcome Summary (Optional)
No response
📄 Relevant Logs or Errors