codesandbox / codesandbox/codesandbox-client
Error 422 - Cannot export sandbox to GitHub
Open
Nobody has claimed this yet.
🐛 Bug
API
GitHub
Needs More Info
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the
Contributing Guidelines
for this project. - 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
Cannot export sandbox to GitHub. The process fails with "No commit found for SHA: main" and the GitHub repo created under my account is empty. Tried logging out then logging back in, issue persists.
How has this issue affected you? What are you trying to accomplish?
Per above
To Reproduce
Link to sandbox: link
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 2d40f51ad |
| Browser | Edge Chromium 89 |
| Operating System | Windows 10 |
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
The report names no source file, test, or entry point. Start by reproducing the export from sandbox awesome-thunder-klb3i and inspect the GitHub export flow around the "No commit found for SHA: main" error. Done means exporting creates a GitHub repository containing the sandbox contents and a valid commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100