codesandbox / codesandbox/codesandbox-client

Cannot access new git branches

Open
#7,662 0 comments 0 reactions 0 assignees View on GitHub

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

  • 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

Any new branches created on a public repository cannot be accessed by codesandbox. The issue has been observed on two different repository, and on multiple newly created branches despite similar code and file structure

How has this issue affected you? What are you trying to accomplish?

Cannot create new version branch to demo within codesandbox.

To Reproduce

New Failing Branches:
https://codesandbox.io/s/github/coveo/atomic-documentation-codesandbox/tree/2.29.0/
https://codesandbox.io/s/github/coveo/atomic-documentation-codesandbox/tree/2.30.1/
https://codesandbox.io/s/github/coveo/atomic-documentation-codesandbox/tree/test/
https://codesandbox.io/embed/github/coveo/headless-documentation-material-ui-react-codesandbox/tree/version-2.17.1/

Existing (Working) branches:
https://codesandbox.io/s/github/coveo/atomic-documentation-codesandbox/tree/latest/
https://codesandbox.io/s/github/coveo/atomic-documentation-codesandbox/tree/2.28.0/
https://codesandbox.io/embed/github/coveo/headless-documentation-material-ui-react-codesandbox/tree/version-2.16.5

Your Environment
Software Name/Version
Сodesandbox 4b6f44df8
Browser Firefox
Operating System MacOS

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the failing and working Codesandbox branch URLs listed in the issue, then trace how public GitHub branches are fetched and opened. Done means newly created public branches load in Codesandbox consistently with the existing working branches; the issue names no source files or tests to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, javascript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.