Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
CI pipeline update
What is the current behavior? (You can also link to an open issue here)
PyPi-push CI only runs on pushes to mainline, does not run unit tests.
The unit tests pipeline also runs on pushes to mainline.
What is the new behavior (if this is a feature change)?
PyPi-push CI now also runs on branches matching the releases/* pattern. The pipeline also runs unit tests, which must pass, before being pushed to PyPi.
The unit tests pipeline no longer also runs on pushes to mainline, as these tests are run in the upgraded push-to-pypi workflow
The unit tests pipeline now also runs on update to PRs matching the releases/* pattern.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Testing
After changes are merged, the follow tests will be run through:
Notes and observations
The GH workflow runs the on-push commands after merging, using the updated workflow.
Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) CI pipeline update
What is the current behavior? (You can also link to an open issue here) PyPi-push CI only runs on pushes to mainline, does not run unit tests. The unit tests pipeline also runs on pushes to mainline.
What is the new behavior (if this is a feature change)? PyPi-push CI now also runs on branches matching the
releases/*pattern. The pipeline also runs unit tests, which must pass, before being pushed to PyPi. The unit tests pipeline no longer also runs on pushes to mainline, as these tests are run in the upgraded push-to-pypi workflow The unit tests pipeline now also runs on update to PRs matching thereleases/*pattern.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No
Testing After changes are merged, the follow tests will be run through:
Notes and observations