Skip to content

fix(crons): Correctly type duration as being nullable #91769

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

Conversation

evanpurkhiser
Copy link
Member

No description provided.

@evanpurkhiser evanpurkhiser requested a review from a team as a code owner May 15, 2025 20:52
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 15, 2025
@evanpurkhiser evanpurkhiser enabled auto-merge (squash) May 15, 2025 21:00
@evanpurkhiser evanpurkhiser merged commit ef23ce0 into master May 15, 2025
60 of 61 checks passed
@evanpurkhiser evanpurkhiser deleted the evanpurkhiser/fix-crons-correctly-type-duration-as-being-nullable branch May 15, 2025 21:11
Copy link

codecov bot commented May 15, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #91769      +/-   ##
==========================================
+ Coverage   87.62%   87.66%   +0.04%     
==========================================
  Files       10337    10336       -1     
  Lines      586492   586046     -446     
  Branches    22543    22543              
==========================================
- Hits       513885   513735     -150     
+ Misses      72162    71866     -296     
  Partials      445      445              

@github-actions github-actions bot locked and limited conversation to collaborators May 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants