ci: add fetch-depth: 0 to qlty checkout for proper git history access

[jamesbhobbs]

ci: add fetch-depth: 0 to qlty checkout for proper git history access

Summary

Updated the qlty job in CI to use fetch-depth: 0 when checking out code. This ensures qlty has access to full git history, which is required for it to properly analyze code changes and run comparisons against previous versions.

Changes:

• Added fetch-depth: 0 to the checkout action in the qlty job
• Updated checkout action to v5 (standardizing with other jobs in the workflow)

Review & Testing Checklist for Human

• Verify CI passes successfully on this PR (qlty check and qlty smells both complete without errors)
• Confirm qlty is now able to access git history and perform proper code analysis
• Check that this change aligns with qlty documentation requirements

Notes

This is part of a coordinated fix across 4 repositories (jupyterlab-deepnote, deepnote, deepnote-internal, vscode-deepnote) to ensure qlty can work properly in all CI pipelines.

Devin session: https://app.devin.ai/sessions/8e83a17c48d34c79be89b985c9b936ee
Requested by: James Hobbs ([email protected], @jamesbhobbs)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[coderabbitai]

Warning

Rate limit exceeded

@jamesbhobbs has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 46 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 1d8386c and 4321043.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (1 hunks)

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.20%. Comparing base (1d8386c) to head (4321043).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #39   +/-   ##
=======================================
  Coverage   50.20%   50.20%           
=======================================
  Files          13       13           
  Lines         249      249           
  Branches       26       26           
=======================================
  Hits          125      125           
  Misses        119      119           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.