-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[DOCS] small fixes for newer DQ use case articles #10847
base: develop
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for niobium-lead-7998 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## develop #10847 +/- ##
========================================
Coverage 80.69% 80.69%
========================================
Files 465 465
Lines 40493 40493
========================================
+ Hits 32676 32677 +1
+ Misses 7817 7816 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ 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.
Great catches! Thank you for fixing these.
This issueless PR removes one mention of suites in the context of the GX Cloud UI as a follow up to #10665 (some newer data quality use case pages were in flight at the same time as the SUJ-E docs updates so I took a look through them to see if there was anything that should be updated to reflect SUJ-E). This PR also fixes some small typos I noticed while looking through these pages
invoke lint
(usesruff format
+ruff check
)For more information about contributing, visit our community resources.
After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!