From 7357e28c85235a1499b51be9b94e5ebf574d997d Mon Sep 17 00:00:00 2001 From: Yasmin Zhamborova Date: Mon, 14 Jul 2025 13:03:12 +0200 Subject: [PATCH] [LK-1496] Update status checks docs --- .../integrating-codacy-with-your-git-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/integrating-codacy-with-your-git-workflow.md b/docs/getting-started/integrating-codacy-with-your-git-workflow.md index 2063b0aaee..5940d79954 100644 --- a/docs/getting-started/integrating-codacy-with-your-git-workflow.md +++ b/docs/getting-started/integrating-codacy-with-your-git-workflow.md @@ -59,7 +59,7 @@ Once you've tested out Codacy for a while and you're happy with the level of fee Follow the instructions from your Git provider to block merging pull requests if they don't pass the Codacy status check: -- **GitHub:** [set Codacy as a required status check](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) +- **GitHub:** set Codacy as a required status check via [branch protection rules](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) or [rulesets](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets#require-status-checks-to-pass-before-merging) - **GitLab:** [only allow merge requests to be merged if the pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html#only-allow-merge-requests-to-be-merged-if-the-pipeline-succeeds) - **Bitbucket:** [configure Bitbucket to prevent a merge with unresolved merge checks](https://support.atlassian.com/bitbucket-cloud/docs/suggest-or-require-checks-before-a-merge/)