-
Notifications
You must be signed in to change notification settings - Fork 262
Description
Describe the bug
Once I create a new repository after using Bolt with StackBlitz for the first time and then rename the repository in GitHub, I don’t see that it’s connected to the same repo when I try to commit updated files later. Is this because I changed the repo name initially? It should allow me to connect to the repository by selecting it, similar to how it works in Replit.
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/rvadhvana/sb1-slpcyr
Steps to reproduce
The error occurs when I create a new repository after using Bolt with StackBlitz for the first time. After creating the repository, I rename it in GitHub. When I try to commit updated files later, I don't see that the repository is connected to the same repo. Is this because I changed the repo name initially? To reproduce the error, you can follow these steps: 1. Create a new repository after using Bolt with StackBlitz for the first time. 2. Rename the repository in GitHub. 3. Try to commit updated files.
Expected behavior
github repo is not connected
Parity with Local
- I have run the project in my local machine and I could not reproduce the issue.
Screenshots
Platform
Version = 1.84.0
Hash = 3b0b7194bc6b567c2eaf4c96a5759098469dcf59
WebContainer = fc837ba8
Browser name = Chrome
Full version = 131.0.0.0
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
performance.memory = {
"totalJSHeapSize": 191941809,
"usedJSHeapSize": 160036417,
"jsHeapSizeLimit": 4294705152
}
Additional context
No response
