[content-init] Workspace images containing files in /workspace break content init
Open
Nobody has claimed this yet.
component: content-service
meta: never-stale
team: workspace
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
When a workspace image contains files in /workspace/${checkoutLocation} the content init fails with
cannot initialize workspace: cannot initialize workspace: git initializer: git clone --depth=1 --no-single-branch https://github.com/your-org/your-repo.git . failed (exit status 128): fatal: destination path '.' already exists and is not an empty directory.
Steps to reproduce
Start a workspace with an image which contains files in /workspace/your-repo
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the content-init path that invokes git clone for /workspace/${checkoutLocation}, then reproduce with an image containing files under that directory. Done means the reported workspace initializes successfully without the destination-not-empty error; no file or test is identified in the issue, so those must be discovered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100