feat(guardrail): support one-sided test #61
Merged
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
) * feat(guardrail): add one-sided input and calculation for single comparison * feat(guardrail): add one-sided calculation for multiple comparisons * update alternative question * add test * update fixed output * remove redundant code * fix patched variable * add todo and update tests * chore(deps): update actions/setup-python digest to 13ae5bb (#56) * feat(guardrail): add one-sided input and calculation for single comparison * reformat Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
xyzou685
requested review from
vjohnson1-godaddy and
dfu-godaddy
and removed request for
vjohnson1-godaddy
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.
This PR combines #46 , #58 and #57
To help us get this pull request reviewed and merged quickly, please be sure to include the following items:
PR Type
What kind of change does this PR introduce?
Backward Compatibility
Is this change backward compatible with the most recently released version? Does it introduce changes which might change the user experience in any way? Does it alter the API in any way?