Amazon CodeCatalyst is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see How to migrate from CodeCatalyst.
Blocking third-party merges when workflows fail
After linking a GitHub or Bitbucket repository to CodeCatalyst, you can add CodeCatalyst workflows for pull requests. Similarly, after linking a GitLab project repository to CodeCatalyst you can add CodeCatalyst workflows for merge requests. One or more workflow runs can occur on a specific commit, and the run status of each workflow in CodeCatalyst is also reflected as part of the commit status in GitHub, Bitbucket, or GitLab. When a new commit is pushed, new workflow run statuses are reflected in GitHub, Bitbucket, or GitLab for that new commit. If you run a workflow again for a commit, the new workflow run status overrides the previous status for that commit and workflow.
You can set branch protection rules in GitHub or Bitbucket to block a pull request merge, or in GitLab to block a merge request, when the latest commit has a failed workflow run status. With branch protection rules, the status of the latest commit affects the ability to merge a pull request in GitHub, Bitbucket, or GitLab. To learn more about workflows, see Running a workflow and Starting a workflow run automatically using triggers.
Depending on which third-party repository provider you're using, see the following:
-
GitHub repositories: GitHub’s documentation About status checks
and About protected branches . -
Bitbucket repositories: Bitbucket’s documentation for Using branch permissions
and Take control with branch permissions in Bitbucket Cloud . -
GitLab repositories: GitLab’s documentation for Auto merge
and Protected branches .
