Separate semver PR label check into its own workflow #36
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.
Separate semver PR label check into its own workflow
Putting this into the Continuous Integration workflow caused the workflow to trigger two times when a PR is created because creating the PR and applying the first label seem to be BOTH triggered. This was causing 9 build jobs to run twice unnecessarily.
This change separates out the semver PR label check into its own workflow. This semver PR label check workflow is still triggered twice when a PR is created with an initial label. At least the Continuous Integration workflow is not triggered twice.