Netlify CLI Branch Deploys

Features
, ,
1

Hello!

So far Netlify has been a great tool to get our website off the ground and quickly running. As we have grown, our CI/CD process has grown as well. One feature that from previous searches in the forums does not exist or not fully is the ability to do branch deploys through the CLI. I think this is possible via alias flag but a “bug” exists where if you had already deployed a branch via the automated approach then the CLI will not override it?

I actually spent quite a bit of time swapping from the automated deploys to BitBucket pipelines and triggering a manual deploy because there are other steps I want to occur before deploying or I want to merge to develop, staging, or master and not trigger a deploy till certain build steps run. I set this all up only to realize the manual deploys do not overwrite my develop and staging environments with the new changes.

Is this feature going to be released or fixed anytime soon? Without being able to manually deploy specific environments it makes Netlify feel like a good starter tool but kind of loses its value as you need to scale.

Thanks.

2

Never say never, but I do not think this will ever be a possibility. CLI deploys are not Git-based, so it would be philosophically wrong to call a CLI-deploy as a branch deploy. For a branch deploy, you need a branch - CLI does not create a branch.

As for your use-case, I think you can create build hooks which run on specific branches. Then you just send a POST request to that URL and it’d trigger a branch deploy. Is that not possible?