docs(kilo-docs): add workspace migration section to KiloClaw FAQ#8287
docs(kilo-docs): add workspace migration section to KiloClaw FAQ#8287kilo-code-bot[bot] wants to merge 2 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
|
|
||
| Ask your Claw to push the workspace to a GitHub repository: | ||
|
|
||
| > Create a new GitHub repo and push your entire workspace there with the `gh` CLI. Tell me the URL of the repo you used. |
There was a problem hiding this comment.
WARNING: GitHub repo backup can produce incomplete restores
Pushing the entire workspace into a new GitHub repository does not faithfully preserve common /root/clawd layouts. Nested project repositories are typically recorded as gitlinks instead of full contents, and anything not committed into the temporary backup repo is dropped on restore. That makes this migration path prone to silent data loss unless it is limited to non-nested workspaces or changed to use an archive-based backup.
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional issues found outside the diff. Files Reviewed (2 files)
Fix these issues in Kilo Cloud Reviewed by gpt-5.4-20260305 · 137,758 tokens |
…AQ page Move the 'Migrating Your Workspace' content from dashboard.md to faq/general.md where it better fits as a frequently asked question. The FAQ version is expanded with a clear what-migrates/what-doesn't breakdown, workspace memory/context note, and step-by-step integration reconfiguration instructions.
kilo-code-bot
bot
changed the title
|
|
||
| Ask your Claw to push the workspace to a GitHub repository: | ||
|
|
||
| > Create a new GitHub repo and push your entire workspace there with the `gh` CLI. Tell me the URL of the repo you used. |
There was a problem hiding this comment.
WARNING: GitHub repo backup can drop embedded repositories
Pushing the whole workspace into a new GitHub repository will not round-trip common /root/clawd layouts. Embedded project repos are typically stored as gitlinks instead of full working trees, so restoring from that backup can silently lose nested repo contents and git metadata unless this step is changed to archive the workspace first.
Summary
dashboard.md) to the FAQ page (faq/general.md) where it is a better fitdashboard.mdto its original state (no migration content)Built for Alex Gold by Kilo for Slack