Skip to content

feature: adds coverage checks to merge queues documentation CF-2414 #2643

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pedrobpereira merged 1 commit into from
Apr 24, 2026
Merged

feature: adds coverage checks to merge queues documentation CF-2414 #2643

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/repositories-configure/integrations/github-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,9 @@

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 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.
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** — and also for **Codacy Coverage Variation** and **Codacy Diff Coverage** if the respective [Gates](../../repositories-configure/adjusting-quality-gates.md) are being enforced.

Check failure on line 100 in docs/repositories-configure/integrations/github-integration.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Dashes] Remove the spaces around ' — '.

Raw Output:
{"message": "[Microsoft.Dashes] Remove the spaces around ' — '.", "location": {"path": "docs/repositories-configure/integrations/github-integration.md", "range": {"start": {"line": 100, "column": 161}}}, "severity": "ERROR"}

When 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 it was already unblocked before joining the queue, always returning green is a safe approach that avoids unnecessary friction.

Check failure on line 102 in docs/repositories-configure/integrations/github-integration.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Dashes] Remove the spaces around ' — '.

Raw Output:
{"message": "[Microsoft.Dashes] Remove the spaces around ' — '.", "location": {"path": "docs/repositories-configure/integrations/github-integration.md", "range": {"start": {"line": 102, "column": 90}}}, "severity": "ERROR"}

## See also

Expand Down
Loading