Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mono - upgrading xo to 0.59.0 #1090

Merged
merged 3 commits into from
Jul 22, 2024
Merged

mono - upgrading xo to 0.59.0 #1090

merged 3 commits into from
Jul 22, 2024

Conversation

jaredwray
Copy link
Owner

@jaredwray jaredwray commented Jul 20, 2024

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
mono - upgrading xo to 0.59.0

Copy link

codecov bot commented Jul 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.49%. Comparing base (3e3eba5) to head (2ffed30).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1090   +/-   ##
=======================================
  Coverage   99.49%   99.49%           
=======================================
  Files          40       40           
  Lines        2993     2993           
  Branches      531      531           
=======================================
  Hits         2978     2978           
  Misses         15       15           

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

@jaredwray jaredwray merged commit c76241c into main Jul 22, 2024
7 checks passed
@jaredwray jaredwray deleted the mono---upgrading-xo-to-0.59.0 branch July 22, 2024 20:53
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.

1 participant