From 2d3feb6638de7a87ef7fd2567fe59945acedc76d Mon Sep 17 00:00:00 2001 From: Pedro Pereira Date: Tue, 30 Jun 2026 10:57:28 +0100 Subject: [PATCH] feature: updates pull request bypass coverage mentions OD-219 --- docs/faq/code-analysis/can-i-bypass-codacy-status-check.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/faq/code-analysis/can-i-bypass-codacy-status-check.md b/docs/faq/code-analysis/can-i-bypass-codacy-status-check.md index e980e8d163..26b1611ff3 100644 --- a/docs/faq/code-analysis/can-i-bypass-codacy-status-check.md +++ b/docs/faq/code-analysis/can-i-bypass-codacy-status-check.md @@ -1,7 +1,7 @@ # Can I bypass Codacy status check? !!! note - **This will only apply to gates enforcing quality checks.** If coverage is blocking a pull request analysis, we recommend contacting your git provider admin or temporarily disabling the coverage gate on the repo and reanalyzing the pull request before enabling them again. + **This will apply to gates enforcing quality and coverage checks.** To protect your code from unwelcome changes, you can [configure your Git workflow to block merging pull requests](../../getting-started/integrating-codacy-with-your-git-workflow.md#blocking-pull-requests) if they don't pass the Codacy status check.