Switch to Block-Style Sequence for Python Versions in build Workflow #83
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
Switch from a flow style to a block style sequence in the build workflow. This will improve maintainability by making version changes impact one Python version at a time.
mcdonnnj
added
the
improvement
jsf9k
approved these changes
Jul 31, 2021
mcdonnnj
added
the
blocked
mcdonnnj
deleted the
improvement/gha_python_version_block_style_sequence
branch
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.
🗣 Description
This PR changes the sequence of Python versions to use for the
testandbuildjobs to use block-style instead of flow-style formatting.💭 Motivation and context
This improves the readability and makes any changes to supported versions a discrete change.
🧪 Testing
With these changes in place the jobs run (and pass) as they did before.
✅ Checklist