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

Maximizer shouldn't offer grim buffs while standard restricted #2196

Merged
merged 1 commit into from Feb 2, 2024

Conversation

Veracity0
Copy link
Contributor

No description provided.

@Veracity0 Veracity0 requested a review from a team as a code owner February 1, 2024 22:22
Copy link

codecov bot commented Feb 1, 2024

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (7a0828c) 37.08% compared to head (35d7e38) 37.07%.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##               main    #2196      +/-   ##
============================================
- Coverage     37.08%   37.07%   -0.01%     
- Complexity    19527    19531       +4     
============================================
  Files          1106     1106              
  Lines        168864   168866       +2     
  Branches      35681    35682       +1     
============================================
- Hits          62615    62613       -2     
- Misses        96280    96289       +9     
+ Partials       9969     9964       -5     
Files Coverage Δ
.../net/sourceforge/kolmafia/maximizer/Maximizer.java 39.76% <0.00%> (-0.07%) ⬇️

... and 4 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a0828c...35d7e38. Read the comment docs.

@Veracity0 Veracity0 merged commit 0130815 into main Feb 2, 2024
8 checks passed
@Veracity0 Veracity0 deleted the grim-standard branch February 2, 2024 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants