-
Notifications
You must be signed in to change notification settings - Fork 919
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
doc: make the chart installation doc easier to understand. #4300
Conversation
/cc @calvin0327 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #4300 +/- ##
==========================================
- Coverage 52.80% 52.01% -0.80%
==========================================
Files 240 242 +2
Lines 23624 23993 +369
==========================================
+ Hits 12474 12479 +5
- Misses 10471 10833 +362
- Partials 679 681 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
/lgtm |
/cc @RainbowMango |
Signed-off-by: jwcesign <[email protected]>
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.
/approve
Thanks.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Paragraph segmentation blurs, making it clearer.
Which issue(s) this PR fixes:
Fixes #none
Special notes for your reviewer:
Does this PR introduce a user-facing change?: