-
Notifications
You must be signed in to change notification settings - Fork 21
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
revert!: remove legacy engines from the flow #157
Conversation
6ec3781
to
b49ef67
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #157 +/- ##
============================================
- Coverage 69.92% 56.35% -13.58%
============================================
Files 26 15 -11
Lines 2148 834 -1314
============================================
- Hits 1502 470 -1032
+ Misses 630 362 -268
+ Partials 16 2 -14 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one comment
Could you take a look at the failing CI? |
b49ef67
to
db0cbfd
Compare
I just updated all the github workflows. It should work now. |
e8ab473
to
b4944ea
Compare
b4944ea
to
d7f3075
Compare
Signed-off-by: Abhinandan Purkait <purkaitabhinandan@gmail.com>
d7f3075
to
e33ce3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
DISABLED cSTOR and JIVA stem commands as these engines are to be made legacy and deprecated.
Changes