Use native concurrency functionality and separate CI and PR actions #1104
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.
What does this Pull Request accomplish?
Migrate to using the native concurrency functionality provided by github actions. This migration was suggested by the styfle/cancel-workflow-action we were using in their README.
Also created a separate ci.yml and pr.yml for easier sorting when looking at the actions tab. This also mimics what other projects like nidaqmx-python and measurement-plugin-labview follow. This also makes it clear on the rules that for PR builds if another action is kicked off it would cancel the previous while the same is not true for CI builds.
Why should this Pull Request be merged?
What testing has been done?
PR build