All topics

Change branch name

Miles

5 months ago

I made the mistake of using an _ in the brand name and now I can't get Google Auth to accept the domain.

Is it possible to change the branch name?
Change branch name
Tom Ireland

5 months ago

Interesting issue, @Miles

I can't do anything about it but I was curious.

Looks like underscores in hostnames are a no-no but okay in domain names (there's some apparent differences I didn't know about). Might be worth the toddle team enforcing dashes for branch names given that could pose an issue when testing auth on branch URLs. They'd be better placed to advise on the technicalities of it.

Alternative would be to publish your branch as-is and then create a new branch and implement auth.
Tom Ireland

5 months ago

I tend to follow a hyphenated approach to branch names, so never ran into this issue.
Miles

5 months ago

Thanks for the reply @Tom Ireland . I can't publish the branch as it's not ready. If I make a new branch, can I sync it with this branch to then continue working on it without publishing?
Tom Ireland

5 months ago

You can create a new branch, yes. This would be created from main though, so will not include any changes from the branch currently open. Providing you don't change anything related to stuff that already exists in main and may have changed in your soft_launch branch, you should be able to sync without issues but you will have merge conflicts otherwise.

Might be worth raising a minor bug in undefined to take into account this use-case and see if there's anything the toddle team can do to help you first. 👍
👍2
Tom Ireland

5 months ago

If there's stuff that should not be seen in your current branch and there's a risk folk might see this on the site, you could put it behind a feature flag. Andreas just published a video on this today. See undefined

You could then publish and not worry about something being seen but I don't know the ins and outs of your project to know if that's a good approach for you, so would be your call.
@Tom Ireland
If there's stuff that should not be seen in your current branch and there's a risk folk might see this on the site, you could put it behind a feature flag. Andreas just published a video on this today. See undefined

You could then publish and not worry about something being seen but I don't know the ins and outs of your project to know if that's a good approach for you, so would be your call.
Miles

5 months ago

I just watched that :). But unfortunately theres just too much. The published branch is a landing page. This branch is essentially the full site (v1)
Jacob Kofoed

5 months ago

You want to be able to publish often in general, so feature flags is the way to go. However, if you really want to just rename, the fastest way today is to create a new branch and manually copy each file over, by first deleting the file on your new branch and then CTRL + C/V from your branch over to the new branch 😕
@Jacob Kofoed
You want to be able to publish often in general, so feature flags is the way to go. However, if you really want to just rename, the fastest way today is to create a new branch and manually copy each file over, by first deleting the file on your new branch and then CTRL + C/V from your branch over to the new branch 😕
Miles

5 months ago

Ok, I have an issue then. Is there anyway this branch name can be changed? Maybe by you guys in the backend? 😁 🙏
Erik Beuschau

5 months ago
I'll see what I can do @Miles 👍
Erik Beuschau

5 months ago

I've changed your branch name from soft_launch to softlaunch now 👍
Miles

5 months ago

Awesome @Erik Beuschau thanks so much 🙏
🙌1

Change branch name

Miles

Tom Ireland

Tom Ireland

Miles

Tom Ireland

Tom Ireland

Miles

Jacob Kofoed

Miles

Erik Beuschau

Erik Beuschau

Miles