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

Switch to sbt-typelevel #411

Merged
merged 13 commits into from
Mar 7, 2023
Merged

Switch to sbt-typelevel #411

merged 13 commits into from
Mar 7, 2023

Conversation

fthomas
Copy link
Owner

@fthomas fthomas commented Mar 7, 2023

No description provided.

@codecov
Copy link

codecov bot commented Mar 7, 2023

Codecov Report

Merging #411 (bf038b6) into master (7404ea3) will decrease coverage by 1.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #411      +/-   ##
==========================================
- Coverage   72.54%   71.42%   -1.13%     
==========================================
  Files           4        4              
  Lines          51       28      -23     
  Branches        0        4       +4     
==========================================
- Hits           37       20      -17     
+ Misses         14        8       -6     
Impacted Files Coverage Δ
...cala/eu/timepit/fs2cron/calev/CalevScheduler.scala 55.55% <0.00%> (-17.78%) ⬇️
.../src/main/scala/eu/timepit/fs2cron/Scheduler.scala 100.00% <0.00%> (ø)
...la/eu/timepit/fs2cron/ZonedDateTimeScheduler.scala 100.00% <0.00%> (ø)
...la/eu/timepit/fs2cron/cron4s/Cron4sScheduler.scala 55.55% <0.00%> (+22.22%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@fthomas fthomas added the build label Mar 7, 2023
@fthomas fthomas merged commit 2cd96e1 into master Mar 7, 2023
@fthomas fthomas deleted the topic/sbt-typelevel branch March 7, 2023 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant