Last year, Bitbucket Cloud introduced custom merge checks. This advanced feature allowed users to go beyond Bitbucket’s built-in branch restrictions and create customized merge criteria for pull requests. Now, we’re expanding this feature to better support large organizations with many repositories. As organizations scale, manually configuring checks at the repository level becomes tedious and prone to inconsistency.

CI/CD workflows are essential for modern software development, enabling scalability, seamless integration, and ease of workflow management. However, migrating these workflows between tools—such as from Jenkins to Bitbucket Pipelines—can feel daunting due to differences in syntax, custom configurations, and repository-specific setups. To address these challenges, we’re thrilled to announce the Jenkins to Bitbucket Pipelines Migration Tool.

We recently spoke with customers who want all the advantages and benefits of being standardized on the Atlassian platform with Bitbucket, with an integrated experience across planning, source control, CI/CD, and beyond, while still being able to take advantage of using GitHub Copilot. In this blog, we’re excited to demonstrate how easy it is to use GitHub Copilot alongside your Bitbucket repos.