-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #205, Remove Duplicate Workflows #224
Fix #205, Remove Duplicate Workflows #224
Conversation
CCB:2021-03-24 APPROVED |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should swap the duplicate so it skips the pull_request instead of the push triggers. I'll approve and merge though and we can examine later.
pull_request: | ||
|
||
env: | ||
SIMULATION: native | ||
OMIT_DEPRECATED: false | ||
|
||
jobs: | ||
|
||
#Checks for duplicate actions. Skips push actions if there is a matching or duplicate pull-request action. | ||
duplicate-job: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we name this step "check-for duplicates"? We can open a new issue for this.
Describe the contribution
Fix #205
Removed the main branch in the static analysis, deprecated build, run, and test, and omit deprecated workflows for push. All four workflows, codeql, static analysis, deprecated build, run, and test, and omit deprecated uses a GitHub action to skip any duplication workflows.
Testing performed
Tested on my forked repository. Created a pull request and pushed changes to test.
Expected behavior changes
The static analysis, deprecated build, run, and test, and omit deprecated workflows now run on all branches when code is pushed. The codeql workflow already allowed this. The changes allow the workflows to run on all branches when users are wanting to test their commits on their forked repos.
The GitHub action used skips push workflows, instead of pull request workflows, and does not cause these skips to fail the checks. So, there should be no duplicate GitHub Actions Workflows.
Additional context
References: https://github.com/fkirc/skip-duplicate-actions/#skip-concurrent-workflow-runs, https://github.com/marketplace/actions/skip-duplicate-actions
Travis CI still runs for all push and pull requests and there are duplicate runs for this tool when tested on the forked repo pull request.
Contributor Info - All information REQUIRED for consideration of pull request
Ariel Adams, ASRC Federal