STF-1604: Analyze the merge commit in CodeQL on pull requests

[oschwald]

The CodeQL init step warns on every run:

1 issue was detected with this workflow: git checkout HEAD^2 is no longer necessary. Please remove this step as Code Scanning recommends analyzing the merge commit for best results.

This removes the git checkout HEAD^2 step and the fetch-depth: 2 it needed. On pull requests, CodeQL now analyzes the merge commit that actions/checkout fetches by default. The init, autobuild, and analyze steps are unchanged.

This PR's own CodeQL run should show no warning in the "Initialize CodeQL" step.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated pull request checkouts to use the default revision and fetch depth.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 4062c493-b380-406b-931d-61af519f8d8f

📥 Commits

Reviewing files that changed from the base of the PR and between c3c4309 and bd130ef.

📒 Files selected for processing (1)

• .github/workflows/codeql-analysis.yml

💤 Files with no reviewable changes (1)

• .github/workflows/codeql-analysis.yml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The CodeQL workflow no longer sets fetch-depth: 2 or checks out HEAD^2 for pull-request events. It uses the revision and fetch depth selected by actions/checkout.

Changes

CodeQL checkout

Layer / File(s)	Summary
Retain checkout action defaults .github/workflows/codeql-analysis.yml	The workflow removes the explicit fetch depth and pull-request-only checkout of HEAD^2. persist-credentials: false remains.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to bd130

The workflow now builds and analyzes the pull-request merge commit as intended. No actionable merge-blocking risk was identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: CodeQL will analyze the merge commit for pull requests.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks out the code,
No extra fetch depth to load.
The chosen revision stays in place,
Credentials keep their guarded space.
Then off I hop along the road!}

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot review overview

🟢 Approval recommended

The focused workflow update correctly removes the obsolete checkout override without affecting analysis steps.

Review effort: Balanced
Findings: None

What changed in this PR

Removes obsolete checkout behavior so CodeQL analyzes pull-request merge commits by default.

Changes:

• Removes custom fetch depth.
• Removes manual checkout of the PR’s second parent.

File	Description
.github/​workflows/​codeql-analysis.yml	Uses the default pull-request checkout for CodeQL analysis.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.