Provide a quality_standard.check function for CI systems to run and validate against a QS #748
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…alidate against a QS
…ather than failed)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linked issue(s)
Fixes: KOL-7891
What change does this PR introduce and why?
Provide a quality_standard.check function for CI systems to run and validate against a QS
This would support CI systems in a more first-class way, allowing for a single check call after results have been pushed, rather than loading QS results and customer processing logic.
TODO:
Ideally allow for reference model to be optional and auto populated, once a model is favorited for a dataset.Please check if the PR fulfills these requirements