-
Notifications
You must be signed in to change notification settings - Fork 565
📖 spelling fixes #4750
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
base: main
Are you sure you want to change the base?
📖 spelling fixes #4750
Conversation
@@ -287,7 +287,7 @@ If the project does not have a badge, the probe returns one OutcomeFalse. | |||
|
|||
**Lifecycle**: stable | |||
|
|||
**Description**: Check that the project has an permissive license. |
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.
this file is actually generated via make generate-docs
, so can you update the corresponding probes/<probename>/def.yml
files, run make generate-docs
and commit the changes?
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.
Oops, done.
Signed-off-by: Ville Skyttä <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4750 +/- ##
==========================================
- Coverage 66.80% 66.72% -0.09%
==========================================
Files 230 249 +19
Lines 16602 18925 +2323
==========================================
+ Hits 11091 12627 +1536
- Misses 4808 5463 +655
- Partials 703 835 +132 🚀 New features to boost your workflow:
|
This pull request has been marked stale because it has been open for 10 days with no activity |
What kind of change does this PR introduce?
Docs update, SSIA.
What is the current behavior?
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?