I am using bolt.new to build my site, and wish to incorporate a blogroll. Doing so requires enabling my Netlify ID function which then requires activating continuous deployment.
After linking/authorizing my GitHub repository, I am led to the configurations page where under “Build settings” the first option for “Branch to deploy” has a dropdown menu, but offers no sub-options within it.
Based on my repo config, this should have “main” available, and I cannot manually insert it. Others have mentioned this issue in the forums, but their fixes were unclear to me.
Further, the knowledge base, and associated chat bot both point to pathways on the Netlify site which do not exist in my interface (e.g. Site configuration > Build & deploy > Continuous Deployment > Branches and deploy contexts). This has me stuck in an endless loop, and I need specific instructions as to how to populate the dropdown menu for “Branch to deploy” with my “main” branch from my repo.
Standing by for feedback and/or request for additional info, Thanks!
There are various suggestions in this thread:
https://answers.netlify.com/t/configure-site-and-deploy-branch-to-deploy-gives-alert-no-results-found/98804
They boil down to:
- Make sure your branch exists and is published
- Try unlinking/relinking it in Netlfy (e.g. The old “Turn it off and back on” trick)
I’m just a volunteer, and do not have the time available to spend writing “step by step” instructions.
Instead of requesting that others “step down” for your benefit, you also have the opportunity to “step up”, especially if working with this tooling is something you plan to do longer term.
On the balance of probability it isn’t actually “broken”, but once you’ve exhausted all the basics, if it still doesn’t work, then it’d be fair to wait for Netlify’s response (although they might not suggest much more, based on previous threads).
Note: The thread I’ve provided does contain some ‘step by step’ git instructions (although as always your mileage may vary).
It may not be why the branch doesn’t show up, but at a glance your repository doesn’t contain anything but a single config file:
