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

chore: Distinguish between EL 7 workarounds and proper config tasks #99

Closed

Conversation

spetrosi
Copy link
Contributor

Enhancement:

Reason:

Result:

Issue Tracker Tickets (Jira or BZ if any):

@spetrosi spetrosi requested a review from richm as a code owner April 23, 2024 20:59
@spetrosi
Copy link
Contributor Author

[citest]

Copy link

codecov bot commented Apr 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.34%. Comparing base (63d7c0c) to head (e42abbc).
Report is 16 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #99      +/-   ##
==========================================
+ Coverage   78.43%   85.34%   +6.91%     
==========================================
  Files           2        2              
  Lines         255      232      -23     
==========================================
- Hits          200      198       -2     
+ Misses         55       34      -21     
Flag Coverage Δ
sanity ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@spetrosi spetrosi marked this pull request as draft April 23, 2024 22:31
@spetrosi spetrosi force-pushed the separate-el7-workarounds branch from e780c38 to e42abbc Compare April 24, 2024 15:59
@spetrosi
Copy link
Contributor Author

[citest]

@spetrosi spetrosi closed this May 9, 2024
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.

2 participants