codesandbox / codesandbox/codesandbox-client
Unable to create the repo.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- [ x] I have read the Contributing Guidelines for this project.
- [ x] I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
I can't "Export the content of this sandbox to a new GitHub repository" .
How has this issue affected you? What are you trying to accomplish?
I am trying to export the contente of the sandbox to GitHub. I already made sure the name of the repo I'm trying to create is completely new.
To Reproduce
Link to sandbox: link (optional)
https://codesandbox.io/s/huckleberry-forked-jwoem?resolutionWidth=1400&resolutionHeight=800
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | Brave |
| Operating System | IOS |
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 reproducing the export-to-GitHub failure from the linked CodeSandbox sandbox, using the reported Brave browser and iOS environment, then trace the repository-creation flow. Done means the sandbox content can be exported to a newly named GitHub repository; the issue names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100