bolt.new cannot open the private Github repository: no access to the repository

[1WorldCapture]

Describe the bug

A Github private repository opened in stackblitz cannot be opened and loaded with bolt.new. When loading this repository using bolt.new, bolt.new reports an error as follows:

Link to the Bolt URL that caused the error

https://bolt.new/~/github.com/1WorldCapture/ship-fast-ts-supabase

Steps to reproduce

1. open the Github private repository in Stackblitz;
2. get the project ID via browser url, e.g. https://stackblitz.com/~/github.com/1WorldCapture/ship-fast-ts-supabase?file=config.ts, the project ID is /github.com/1WorldCapture/ship-fast-ts-supabase;
3. Construct the bolt.new address (https://bolt.new/~/ and open it with your browser;
4. bolt.new initializes and imports with the error "You don't have access to the repository"

Expected behavior

Expect bolt.new to load private repository projects in stackblitz correctly, and to be able to modify the project code through bolt.new's dialogs properly

Screen Recording / Screenshot

No response

Platform

• OS: Windows
• Browser: Chrome
• Version: 129.0.6668.90

Additional context

No response

[tiagoefreitas]

I also need this to edit my existing projects or to start from a template

[1WorldCapture]

I also need this to edit my existing projects or to start from a template

Agree. If we need to build something real, it must start from some base (existing project or own project template), not blank template......

[kirjavascript]

Hi! 👋 Thanks a lot for the report!

We're tracking this issue internally and will let you know when we have a resolution.

[danielpox]

I created a project using Bolt, and then I opened it in Stackblitz and from there I created a Github repository. I made it private, and I can make changes in the Stackblitz editor, but the connection to Bolt is lost. And as mentioned in this issue, if I try to open the repo in Bolt using the correct link structure, I get the import failed message.

Also I thought upgrading to the paid Pro plan would solve the issue, but those $9 did not help. 😅

[1WorldCapture]

Hi! 👋 Thanks a lot for the report!

We're tracking this issue internally and will let you know when we have a resolution.

Glad to hear this issue is on track, and pls. help speed this problem solving up, it's really important for bolt.new to be production tool

[lipecss]

I created a project using Bolt, and then I opened it in Stackblitz and from there I created a Github repository. I made it private, and I can make changes in the Stackblitz editor, but the connection to Bolt is lost. And as mentioned in this issue, if I try to open the repo in Bolt using the correct link structure, I get the import failed message.

Also I thought upgrading to the paid Pro plan would solve the issue, but those $9 did not help. 😅

I also noticed this problem

[136sergio]

Bolt is still not able to open private github repositories, you must change your repository to public and it will open-

[Jonkitonki]

Did anyone archieve some progress on this issue? It would be great to keep some projects on private in github :-)

[Veeeetzzzz]

Did anyone archieve some progress on this issue? It would be great to keep some projects on private in github :-)

Yeah +1 - I can use public repos and I'd happily upgrade to a Teams plan if I was working with organisational information that needs to stay private. Right now I'm just making the repos I need to import into Bolt.new public and then reverting or creating a public fork to work off.

Will be so good when this is implemented.

[caingillis]

I upgraded to a Teams plan, this issue still persists even with a Teams plan. Agreed, once this issue is resolved Bolt will be unstoppable!

[Nic-Tai]

i still face this issue. may i know what's the solution?

[iampawan]

Is there any workaround for this problem for now? @kirjavascript

[kirjavascript]

Is there any workaround for this problem for now? @kirjavascript

I'm afraid the only workaround for now is copying the bits you need for bolt into a public repo.

[Greyvend]

@kirjavascript any ETA on when this might be fixed?

[codetesta2z]

This is really defeating the overall purpose of using bolt. Can we expedite it please.

[fvrlak]

It has been almost two months, and the issue still hasn't been solved.

I don't understand the thinking of bolt.new team. Do they really think that importing private repo from github is not essential?

What am I supposed to do with the project after being developed? Put it as public and then copy a link and make it private again?

It is such an important thing even essential thing to have an option to get repo imported back to bolt, that now currently I am not even using the app simply because there is no point in creating any new application.

If it is for some reason not possible to make it via github, then at least it could be possible to upload the folder from pc.

[jannikMetzner]

It has been almost two months, and the issue still hasn't been solved.

I don't understand the thinking of bolt.new team. Do they really think that importing private repo from github is not essential?

What am I supposed to do with the project after being developed? Put it as public and then copy a link and make it private again?

It is such an important thing even essential thing to have an option to get repo imported back to bolt, that now currently I am not even using the app simply because there is no point in creating any new application.

If it is for some reason not possible to make it via github, then at least it could be possible to upload the folder from pc.

same here, have to stop using bolt.new, because I can't sustain my dev process without tracking changes in git

[Tyberious]

Not sure why this wasn't and still isn't implemented out of the gate, not having it defeats the majority of its purpose.

[yashcrest]

You could you use the bolt to github extension in chrome and follow this tutorial
https://www.youtube.com/watch?v=d9NqXRoroi0

[Greyvend]

You could you use the bolt to github extension in chrome and follow this tutorial youtube.com/watch?v=d9NqXRoroi0

It temporarily creates a public copy of your private repo, which is not secure. It's possible just to make your private repo public, then import, then switch it back, but that's an unacceptable workaround for many.

Besides, there needs to be a way to sync changes between the GitHub repo and the Bolt project continuously.

[eksno]

Big issue for me too. Got a team plan for this purpose just to realize it doesn't support private repositories...

[avelops]

Any news on this issue?