Bitbucket Pipelines already supports triggering on repository pushes and pull request pushes. But if you wanted to react to other events like a deployment finishing, a build failing, or a PR getting merged, you had to wire that up yourself with webhooks or external glue code. New trigger types let you define those conditions directly in your YAML. You can fire custom pipelines on events like pipeline-completed, deployment-completed, pullrequest-created, pullrequest-fulfilled, and more. In this video, we walk through how to set up these triggers in your bitbucket-pipelines.yml file so you can chain stages together, send notifications on failures, or generate release notes on merge without building external orchestration. Learn more about new Bitbucket Pipelines trigger types: https://www.atlassian.com/blog/bitbucket/new-triggers-for-pipeline-deployment-and-pull-request-events About Atlassian: Behind every great human achievement, there is a team. From medicine and space travel to disaster response and pizza deliveries, we help teams all over the planet advance humanity through the power of software. Our mission is to help unleash the potential of every team. Connect with Atlassian: Subscribe: https://www.youtube.com/@Atlassian Follow Atlassian on LinkedIn: https://www.linkedin.com/company/atlassian Follow Atlassian on Instagram: https://instagram.com/atlassian Follow Atlassian on X: https://twitter.com/atlassian Follow Atlassian on Facebook: https://facebook.com/atlassian

 223      9