Why was my deployment bypassed?
There are two major reasons a deployment can get bypassed: no changes were found or there was a newer deployment triggered before this one was started.
No changes found in the repository path
When you trigger a deployment, DeployBot will check that you've made changes in the specific repository path you've set up. If we don't find changes, we'll skip the deployment. You want to make sure to check the repo path you've specified and make sure that you made a change in that directory/branch.
A newer deployment was triggered
When a deployment is triggered, it gets queued up to go out. It usually takes only a few seconds, but there can be a chance that someone triggers a newer deployment in that time. In this case, we'll skip the first one and deploy the newer one since you always want newer changes on your server.