- Notifications
You must be signed in to change notification settings - Fork1k
chore: cancel concurrent builds with native feature#116
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Use the native 'concurrency' configuration feature to cancelconcurrent builds, rather than the cancel-workflow-action.This also allows us to reduce permissions for the workflow.
codecovbot commentedFeb 1, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## main #116 +/- ##==========================================+ Coverage 68.92% 71.93% +3.00%========================================== Files 86 91 +5 Lines 3447 3670 +223 Branches 59 59 ==========================================+ Hits 2376 2640 +264+ Misses 883 813 -70- Partials 188 217 +29
Continue to review full report at Codecov.
|
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.
Neato!
| # Cancel in-progress runs for pull requests when developers push | ||
| # additional changes | ||
| concurrency: |
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.
Use the native 'concurrency' configuration feature to cancel
concurrent builds, rather than the cancel-workflow-action.
This also allows us to reduce permissions for the workflow.