From f3848338b1e9a6c409ec44d162ac01783549add5 Mon Sep 17 00:00:00 2001 From: Pedro Pereira Date: Fri, 17 Apr 2026 10:03:58 +0100 Subject: [PATCH 1/2] feature: adds merge queues docs CF-2398 --- .../which-permissions-does-codacy-need-from-my-account.md | 5 +++++ .../integrations/github-integration.md | 6 ++++++ 2 files changed, 11 insertions(+) diff --git a/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md b/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md index eb15a13529..b6b40b9186 100644 --- a/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md +++ b/docs/getting-started/which-permissions-does-codacy-need-from-my-account.md @@ -67,6 +67,11 @@ If you log in with GitHub, Codacy requires the following [app permissions](https Read-Only Codacy retrieves repository contents to get installation access tokens when integrating with your repositories and clone them, and for code coverage analysis.
Codacy requests this permission since September 2023. Make sure an organization owner approves Codacy GitHub App updated permissions on your GitHub organization. + + Merge groups + Read-Only + Codacy listens for the `merge_group` webhook event and responds to the `checks_requested` action accordingly. + Organization permissions: diff --git a/docs/repositories-configure/integrations/github-integration.md b/docs/repositories-configure/integrations/github-integration.md index 2155ac78e1..4a11bf3ec9 100644 --- a/docs/repositories-configure/integrations/github-integration.md +++ b/docs/repositories-configure/integrations/github-integration.md @@ -90,6 +90,12 @@ Adds comments on the lines of the pull request where Codacy finds new issues wit ![Comment suggesting a fix on GitHub](images/github-integration-suggest-fixes.png) +## Merge queues {: id="merge-queues"} + +To support GitHub **merge queues**, our GitHub App requires **Merge Groups** permissions so it can listen for and respond to the `checks_requested` action for merge group events. + +When a merge group event is triggered for a pull request in the merge queue, Codacy automatically sends a green status check to the relevant commit. By the time a pull request enters the merge queue, it has already gone through Codacy's analysis — either receiving a green status or being manually bypassed. Since the pull request was already unblocked before joining the queue, always responding with green is a safe and practical approach that keeps things moving without unnecessary friction. + ## See also - [Integrating Codacy with your Git workflow](../../getting-started/integrating-codacy-with-your-git-workflow.md) From 4049cf5c6a2c23f2604cc4fb0c990942f777e444 Mon Sep 17 00:00:00 2001 From: Pedro Pereira Date: Fri, 17 Apr 2026 10:03:58 +0100 Subject: [PATCH 2/2] feature: adds merge queues docs CF-2398 --- docs/repositories-configure/integrations/github-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/repositories-configure/integrations/github-integration.md b/docs/repositories-configure/integrations/github-integration.md index 4a11bf3ec9..6b01ccf443 100644 --- a/docs/repositories-configure/integrations/github-integration.md +++ b/docs/repositories-configure/integrations/github-integration.md @@ -94,7 +94,7 @@ Adds comments on the lines of the pull request where Codacy finds new issues wit To support GitHub **merge queues**, our GitHub App requires **Merge Groups** permissions so it can listen for and respond to the `checks_requested` action for merge group events. -When a merge group event is triggered for a pull request in the merge queue, Codacy automatically sends a green status check to the relevant commit. By the time a pull request enters the merge queue, it has already gone through Codacy's analysis — either receiving a green status or being manually bypassed. Since the pull request was already unblocked before joining the queue, always responding with green is a safe and practical approach that keeps things moving without unnecessary friction. +When a merge group event is triggered for a pull request in the merge queue, Codacy automatically sends a green status check for **Codacy Static Code Analysis** to the relevant commit. By the time a pull request enters the merge queue, it has already gone through Codacy's analysis — either receiving a green status or being manually bypassed. Since the pull request was already unblocked before joining the queue, always responding with green is a safe and practical approach that keeps things moving without unnecessary friction. ## See also