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

fix: Consequences display (#116) #129

Merged
merged 1 commit into from
Oct 16, 2023
Merged

Conversation

gromdimon
Copy link
Contributor

Consequences are present correctly now.

@gromdimon gromdimon linked an issue Oct 16, 2023 that may be closed by this pull request
@gromdimon gromdimon enabled auto-merge (squash) October 16, 2023 12:30
@codecov
Copy link

codecov bot commented Oct 16, 2023

Codecov Report

Merging #129 (06671df) into main (555fae4) will increase coverage by 2.59%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #129      +/-   ##
==========================================
+ Coverage   80.49%   83.08%   +2.59%     
==========================================
  Files          91       31      -60     
  Lines        2840      479    -2361     
  Branches      738        0     -738     
==========================================
- Hits         2286      398    -1888     
+ Misses        514       81     -433     
+ Partials       40        0      -40     

see 60 files with indirect coverage changes

@gromdimon gromdimon merged commit d4c5e3f into main Oct 16, 2023
9 checks passed
@gromdimon gromdimon deleted the 116-consequences-display-is-broken branch October 16, 2023 12:35
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.

Consequences display is broken
1 participant