Skip to content

Conversation

@ReenigneArcher
Copy link
Member

Description

Fix required after LizardByte/.github#480

Screenshot

Issues Fixed or Closed

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Jul 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.39%. Comparing base (1a80c2e) to head (2100b10).
Report is 1 commits behind head on master.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #428      +/-   ##
==========================================
+ Coverage   60.30%   60.39%   +0.08%     
==========================================
  Files          21       21              
  Lines        1164     1164              
==========================================
+ Hits          702      703       +1     
+ Misses        462      461       -1     

see 1 file with indirect coverage changes

@ReenigneArcher ReenigneArcher merged commit af97a3d into master Jul 14, 2025
17 checks passed
@ReenigneArcher ReenigneArcher deleted the ReenigneArcher-patch-1 branch July 14, 2025 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants