[Vincent Biret (baywet)]

Summary

Add plain merge_group: triggers (null value, without an explicit types restriction) to the three workflows producing required Actions checks. Existing jobs have no PR-only event conditions or payload references and already use the checked-out event revision, so no job changes are needed.

Required-check evidence

Reviewed recent merged PR #2237 (merged November 5, 2026).
gh pr checks 2237 --required and the effective rules endpoint (repos/microsoft/kiota-java/rules/branches/main, active ruleset 26719695) agree on these required checks:

Required check	Workflow / provider	Reviewed run
build	.github/workflows/build.yml (Gradle Build And Test)	https://github.com/microsoft/kiota-java/actions/runs/41926319933
lint-api-level	.github/workflows/api-level-lint.yml	https://github.com/microsoft/kiota-java/actions/runs/41926319356
Analyze (java)	.github/workflows/codeql.yml (CodeQL)	https://github.com/microsoft/kiota-java/actions/runs/41926319153
license/cla	External Microsoft GitHub Policy Service app	Not an Actions workflow; unchanged

Run metadata confirms the three workflow paths. Other observed checks (including Build, SonarCloud and changelog guard) are not required by the effective status-check rules and are intentionally unchanged. No rules or merge settings are changed.

Validation

• Read repository CONTRIBUTING guidance; isolated worktree based on origin/main, original checkout/index left unchanged.
• git diff --check: passed.
• Exact-content assertions: only one plain merge_group: trigger line added per workflow; no PR-only event/payload coupling.
• Actionlint: unfiltered baseline and changed files both report the same pre-existing undefined inputs.componentName in build.yml. With only that exact diagnostic ignored, all three changed workflows pass. This unrelated issue is not changed here.
• No Java tests run: changes only enable existing workflows on another event.

Limits

Classic branch protection endpoint returned HTTP 404, but effective branch rules and required PR checks were accessible and consistent. External CLA merge-queue behavior is not controlled by these workflows. Actual merge-group execution must be verified when queued after landing; this PR does not merge or enqueue anything.

[Copilot]

🟢 Approval recommended

No active review issues were identified for the changes enabling required workflow checks on merge-queue groups.

No open issues 🎉

What changed in this PR

Enables the three workflows that produce required Actions checks to run for merge-queue groups, so queued changes can receive those checks.

Changes:

• Adds merge_group with types: [checks_requested] to the build, API-level lint, and CodeQL workflows.
• Leaves existing triggers, jobs, branch rules, and the external CLA check unchanged.

File	Description
.github/​workflows/​codeql.yml	Enables CodeQL analysis for merge groups.
.github/​workflows/​build.yml	Enables Gradle build and tests for merge groups.
.github/​workflows/​api-level-lint.yml	Enables API-level compatibility checks for merge groups.

_{Review effort: Balanced}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

🟢 Approval recommended

No active review issues remain for the workflow-trigger updates supporting merge-queue validation.

No open issues 🎉

_{Review effort: Balanced}