Hello,
The git branch deploy using github repository is working great. The default URL is vease.netlify.app and we have redirections to the master branch with vease.geode-solutions.com and to the next branch next.vease.geode-solutions.com.
The problem is: the Netlify git commit triggers the build too soon for our pipelines workflows, and dependencies are not yet available. We would like to trigger it by hand so we have a better control.
We tried Netlicy API, CLI and build hooks but none of them create a branch deploy that we can redirect to next.vease.geode-solutions.com.
Thanks for your help
Thanks for the quick reply.
Not sure how to use build hooks to create a branch deploy. It can trigger a new build and create a deploy but it is not published in a branch deploy like a git trigger can do and so not accessible using next.vease.geode-solutions.com
Build hook accepts a trigger_branch query param which should do what you need. That’s what a lot of folks use currently.
Ok Thanks a lot!
Is there a way to stop all triggers from git to only do the one using the build hooks? I do not want to waste build resources if I know it is not up-to-date
Yeah, there’s a hidden setting that we need to enable. I’ll send this to the helpdesk where this can be actioned.
1 Like
Hey @BotellaA 
,
Thanks for reaching out!
We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.
Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.
We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.
Thanks for being here, and keep an eye out for that email from us!
The above is an automated response from a button that we click to send stuff to the helpdesk. Ideally, I’d advise you to follow-up in the ticket email that you’d get when the team responds, but I’ve opened this thread as well in case you want to continue some discussion here.
Thanks a lot!
Sorry but I still have a question: how to login on netlify.okta.com is it a different login than Netlify? My password does not work.
You should not be logging there. You’ll get a reply on the email.