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.
Break up actions into one that does linting and tests python build and other that builds and publishes the wheel
Idea is to have the action that does linting and tests that the python package builds correctly run on every push on every branch while the building and publishing the wheels only runs when a change into master occurs.
One thing to think about is the PyPI wheel publishing will ALWAYS fail if the version number was not bumped as we cannot publish a wheel with the same version as wheels previously published to PyPI
This means any PR that has meaningful changes that we want to immediately propagate to PyPI versions of diploshic MUST include a bumped version number