markdown table format fixes - #13848
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13848 +/- ##
============================================
- Coverage 19.65% 19.64% -0.01%
Complexity 19790 19790
============================================
Files 6368 6368
Lines 574889 574889
Branches 70353 70353
============================================
- Hits 112966 112963 -3
- Misses 449649 449655 +6
+ Partials 12274 12271 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 2 changed files in this pull request and generated no new comments.
Suppressed comments (2)
plugins/storage/volume/ontap/README.md:41
- These tables use a double leading pipe (
||), which in standard GitHub/CommonMark table parsing renders as an extra empty first column. If the intent is a 2-column table, switch rows to a single leading pipe (| Package | Description |) throughout the table (and similarly for the other tables in this README) so the rendered documentation doesn’t include a blank column.
| Package | Description |
| --- | --- |
| `driver` | Primary datastore driver implementation |
plugins/storage/volume/ontap/README.md:74
- The PR description/template appears unfilled (no change type selected, no testing notes). Since the template explicitly notes automation relies on it, please select the appropriate change type and add a brief testing note (even if it’s just “markdownlint only”).
When creating an ONTAP primary storage pool, provide the following details in the URL field (semicolon-separated key=value pairs):
🔴 Test Coverage Grade:
|
| Metric | Value |
|---|---|
| Line coverage | 24.50% |
| Branch coverage | 18.67% |
Grade Scale
| Grade | Line Coverage | Meaning |
|---|---|---|
| 🟢 A | ≥ 80% | Excellent - this code sleeps well at night 😴 |
| 🟡 B | 60-79% | Good - almost there, don't stop now 😉 |
| 🟠 C | 40-59% | Acceptable - your code is wearing a seatbelt, but no airbags 😬 |
| 🔴 D | 20-39% | Marginal - boldly shipping where no test has gone before 🖖 |
| ⛔ F | < 20% | Failing - tests? what tests? 🔥 |
Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run
83b8eb2 to
bc1677d
Compare
|
🔴 Test Coverage Grade:
|
| Metric | Value |
|---|---|
| Line coverage | 24.50% |
| Branch coverage | 18.67% |
Grade Scale
| Grade | Line Coverage | Meaning |
|---|---|---|
| 🟢 A | ≥ 80% | Excellent - this code sleeps well at night 😴 |
| 🟡 B | 60-79% | Good - almost there, don't stop now 😉 |
| 🟠 C | 40-59% | Acceptable - your code is wearing a seatbelt, but no airbags 😬 |
| 🔴 D | 20-39% | Marginal - boldly shipping where no test has gone before 🖖 |
| ⛔ F | < 20% | Failing - tests? what tests? 🔥 |
Branch coverage is shown as a secondary signal. Grade is determined by line coverage.
View full Actions run
Description
This PR… follows on #12943 after the extra markdown lint rule came into effect.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?