Harmony 1838 - Clarify supported python versions #91
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
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.
Jira Issue ID
HARMONY-1838
Description
Clarifies supported python versions (to address What is the minimum python version? #78)
Updates some deprecated GitHub actions.
Modifies the "Tests" GitHub workflow so that detailed HTML code coverage reports are only uploaded to GitHub on pull request open or synchronize events. (For every commit, the tests will still run and the code coverage summary will still be printed to the GitHub actions web UI). If developers want the full HTML coverage report outside of pull requests, it can be generated locally, on demand via
make test.Local Test Steps
run
make ciPR Acceptance Checklist