The Branch Subdomains widget is not showing my new branches.
Previously I successfully built and deployed from one branch (e.g. “test”). Since then, I’ve created a new branch (e.g. “test2”) and that has been pushed to my remote Gitlab repo.
However when I visit Netlify App – the new branch is not available to be selected. Adding the branch name first as a deploy context at Netlify App does not affect this.
Q1 – how long after a branch is created should we see it as an available choice in the Branch Subdomains widget?
Q2 – is there a way to trigger whatever process scans for the new branches so there isn’t a waiting period?
I am facing the same issue. I can attach screenshots to show you what I mean. Unfortunately, I am a new user so I will be attaching the screenshots via an imgur link
hey there, first of all, thanks for taking the time to bring this up! Secondly, i’ve talked with my team about this and you are actually seeing things work as intended. You will need to actually deploy on a branch to see it show up in the UI as a possibility for a branch subdomain.
Can you test this out by making a deploy of a branch, and then seeing if you can add it as a branch subdomain?
Just want to note, that you are right, the staging branch DID show up but only after ~24-48hours. For anyone reading this thread in the future, you might have to for a bit before the github and netlify servers sync up!
that’s great to know, @an732001. I’ll check in with some folks and see if that is something we can make more clear or maybe even speed up a bit. glad it is working now.
I’m running into this same issue; I created a new branch on my repo, with the intent to use a subdomain with it, somewhere around eight hours ago. It’s still not showing up in the Netlify UI.
It’s not a big deal to wait in my case, but I just wanted to cast a +1 vote for a little faster, or more on-demand retrieval of branches.
Good question. Yes, I did push a commit to the branch, though I’m not exactly sure when now that you mention it. I know it was yesterday though.
I just checked again and the branch still isn’t available yet in the Netlify UI, however. So I’m not sure exactly how long it’s been, but I’d say between 24 and 32 hours, roughly.
Sadly, still nothing. I double-checked that I pushed to the branch, and confirmed that it was pushed around 11am CDT two days ago. Tried refreshing the Netlify UI as well just to be sure, but nothing yet.
Hi, @collinsworth. Did you add the branch to the site’s list of branches it will build. This is found under Site Name > Settings > Build & deploy > Continuous Deployment > Branches.
If using a URL, you can replace <site subdomain> with the actual subdomain below:
If you go to that page, is the branch you pushed to listed under “Branch deploys” (or is “Deploy all the branches” selected)?
If the answer is “yes” and you still don’t see the branch deploys, would you please tell us which site this is happening for? (You can tell us the subdomain or the site id.)
You can post that information publicly or you can private message (PM) that to one of our support staff. I’ve confirmed that PMs are enabled for your forum login. Please keep in mind that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.
Ok, so the branch I’m trying to add was not listed under the build branches. I did add it just now, and even re-deployed just to be safe. It doesn’t seem to have fixed the issue, but maybe now it will be picked up eventually…?
Also: oddly, several other branches that are also not listed as build branches do appear in my list of potential branch subdomains. (I am assuming maybe this is because the setting was “all branches” at one point, but now is not.)
The project is called “quina” if you’d like to take a look.
Sorry, maybe I wasn’t clear, but what I’m trying to do is add one of those branches as a custom subdomain (under “Branch subdomains” in the site’s domains settings). I’ve been able to do so successfully with one, but the new branch I just created still builds fine; no issues there. I just can’t select it under “branch subdomains” because it will not appear in the list.
Before the new branch will be available for the branch subdomains there must be a successful deploy for the new branch first.
At this time, I don’t see any successful deploys for the newly added branch. If you push a new commit to that upstream repo on that branch it should trigger a deploy at Netlify. If that deploy is successful, you will be able to add the branch name as a branch subdomain.
All right, that did it. As a recap for those who might land here in the future trying to enable a branch subdomain:
Make sure the branch is enabled for builds. This is in Site Settings > Build & Deploy > Continuous Development > Branches.
Make sure there’s a successful branch deploy.
I ran into a lot of confusion with both of those, because:
When I tried to add a branch subdomain, I saw lots of branches listed that weren’t enabled in the deploy settings. There’s also nothing in the UI to suggest why a branch might or might not appear in the “Branch subdomains” card, and I’d love to see some kind of a callout there highlighting the requirements for a branch to appear in the list.
It was not clear to me that a branch deploy is not the same as a deploy preview. If I’m wrong about that, please correct me. But I did have successful deploy previews of my branch successfully built and available, and it wasn’t until I followed those directions and did an actual branch deploy that the branch showed up as an option in Branch subdomains. That seems weird; there was a build, it just wasn’t the right kind of build, I guess?
Also, for what it’s worth, there are still several branches that are explicitly excluded from builds listed as options under the Branch subdomains dropdown. I suspect perhaps they were fetched back when the site was set to build all branches, and there may not be a pruning mechanism (or if there is, it’s on a substantial delay).
Anyway, thank you for all your help. I definitely wouldn’t have gotten here without it. Hopefully the feedback/recap above is helpful in preventing future issues.
