One issue with this workaround: if your preview branch is a new website, then all updates to the preview branch trigger a new build. Ideally I’d like to set it up so that
1.) The status badge is for a build to the preview branch
2.) The preview branch does not build on push, and is only triggered by a webhook.
However, you can’t turn off builds for a website on push and allow web hooks to trigger builds on the production branch (which, in this workaround, for the ‘preview’ version of the website, needs to be the preview branch). The proposed workaround for this issue is to use branch you never update for your production branch and a branch-deploy for the webhook: which means we’re back to the same problem with the badge not showing the status of a branch deploy.