Skip to content

Conversation

@eivindjahren
Copy link
Contributor

@eivindjahren eivindjahren commented Dec 4, 2025

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'just rapid-tests')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Add backport label to latest release (format: 'backport release-branch-name')

@eivindjahren eivindjahren added the release-notes:maintenance Automatically categorise as maintenance change in release notes label Dec 4, 2025
@codecov-commenter
Copy link

codecov-commenter commented Dec 4, 2025

Codecov Report

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #12450   +/-   ##
=======================================
  Coverage   90.55%   90.55%           
=======================================
  Files         432      432           
  Lines       29296    29285   -11     
=======================================
- Hits        26529    26520    -9     
+ Misses       2767     2765    -2     
Flag Coverage Δ
cli-tests 37.73% <ø> (+0.07%) ⬆️
gui-tests 69.44% <ø> (+0.04%) ⬆️
performance-and-unit-tests 74.08% <ø> (-0.01%) ⬇️
test 38.60% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-notes:maintenance Automatically categorise as maintenance change in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants