Bolt.diy Github repo not showing 'Stable' branch

[shawn]

Hi guys. I’m sure I’ve done something wrong but can’t find the Stable branch. Only showing Main currently. And I’m pretty sure Main get’s all the PR’s applied to it so that’s possibly not great right now.

Anyone tell me what I’ve done wrong please…?

I can find Stable on the Bolt.diy page and assume that’s the one I should have forked from.

I can’t find where in my settings that it says which branch I forked fro now.

Also see changes in the following guide appears out of date…

deploying-bolt-diy-with-cloudflare-pages-the-easy-way

Step 10 for instance…

Missing the Runtime and Bindings from Settings now - or is that only visible on the build cycle…?

[aliasfox]

When you fork the repo there is a checkbox, that is checked by default, to only include the main branch. You want to uncheck it before forking.

It’s in the Cloudflare Pages post instructions, but it’s easy to miss. There is no simple or good way to fix this, so I’d suggest re-forking it.

[shawn]

I knew this was going to be the answer.

So you’re saying I’m Forked…!!

I did have a good look around and Cloudflare also shows it’s not a direct option but I’m sure there’s a way to fix it - but like most things it’s easier to just go back and start again.

And embarrassingly, earlier I mentioned I couldn’t find the Runtime and Bindings Settings. That’s because I was looking uder Github Settings instead of Cloudflare Settings. I can see now why because I was frustrated and had been going in circles. Go to bed and try again in the morning with fresh eyes.

Easiest way now is using that red ‘Delete’ at the bottom and in 2 mins I’ll be fresh again.

[shawn]

@aliasfox - Just on the currency of that guide. Do we still need to complete the compatibility step as below as I assume that will be out of date at some time?

[aliasfox]

I’m not sure the date is strictly needed at all tbh because it worked for me once without it. It’s just what was set in the wrangler.toml file. However the other flag is required.

[shawn]

Sweet - I’ve just completed a fresh build and it’s clear the more you do this, the luckier you get. Haha. I mean, you become more familiar with everything hence my question about the compatibility date. If I find a reason to modify this due to ‘in-compatibility’ then I’ll let you you.

[shawn]

And I’m struggling again with the simplest request - yes I have the correct API key and the error alert doesn’t help at all. It’s just a frustrating component and offers no assistance. I have seen many users complaining about the same thing. Is there any future enhancements that might improve the error alert ?

I’ve changed the default settings and switched off use Main Branch here - don’t know if that is functional here as testing showed no change ?

Argh…

Change to Google - Gemini 2.0 Flash

You can see how frustrating this process can be. If there was some sort of intuitive error alerting that identified the actual issue, then that would be so helpful.

[aliasfox]

I’m personally unsure what the issue is, but as a note the “Optimized” prompts were made for everything other than Claude 3.5 Sonnet because that was already the default of Bolt.New. The issue could have something to do with it but likely seems to be more rooted than that.

Can you confirm that the API works outside of Bolt.diy?

[shawn]

Embarrassing.

I must have ripped through my last credits trying to test and find an error.

I’ll top it up and have a play after.

Sorry I should have checked.