Skip to content

Conversation

dreambeyondorange
Copy link
Contributor

… install check

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@codecov
Copy link

codecov bot commented Aug 8, 2023

Codecov Report

Merging #2406 (f542aa5) into release-3.7 (b87af32) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release-3.7    #2406   +/-   ##
============================================
  Coverage        70.34%   70.34%           
============================================
  Files               13       13           
  Lines             1851     1851           
============================================
  Hits              1302     1302           
  Misses             549      549           
Flag Coverage Δ
unittests 70.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@dreambeyondorange dreambeyondorange merged commit ae692ae into aws:release-3.7 Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants