codesandbox / codesandbox/codesandbox-client

When committing, it sends me the ENTIRE repository (which is already on github)

Open
#7,659 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

My bug is the following, I have my environment connected to my repository, and I send the changes through codesandbox, but for a few days, when I go to send the changes I get the WHOLE environment again, as if it were the first commit , and when sending it, an error appears, although the changes are sent, it is very annoying to see the whole environment to send to github.
image

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

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

To Reproduce
Link to sandbox: link (optional)
Your Environment

| Software | Name/Version |
| Windows | 10 |
| Сodesandbox | |
| Browser |Chrome (lasted)|
| Operating System | |

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

The report names no source file, test, or code entry point. Start by reproducing the GitHub commit flow in CodeSandbox with the reported Windows 10 and Chrome environment, then trace why the entire repository is selected; done means only changed files are sent and the commit completes without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
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.