-
Notifications
You must be signed in to change notification settings - Fork 0
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
Configure concurrency for all CI. #106
Configure concurrency for all CI. #106
Conversation
Signed-off-by: Yury-Fridlyand <[email protected]>
@@ -18,6 +18,10 @@ on: | |||
permissions: | |||
contents: read | |||
|
|||
concurrency: | |||
group: C#-${{ github.head_ref || github.ref }} |
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.
just in case, can you call it csharp-
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.
or dontnet-
@@ -14,6 +14,10 @@ on: | |||
- benchmarks/utilities/* | |||
- .github/workflows/lint-ts.yml | |||
|
|||
concurrency: | |||
group: node-lint-${{ github.head_ref || github.ref }} |
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.
this one is quick, no? I'm not sure why we have a separate workflow for this, but do we really care?
...I mean, it also doesn't hurt.
252b071
into
ci/integ_yuryf_ci_concurrency
Restore CI concurrency removed in valkey-io#991.
To avoid conflicts between different CI workflows, every group name contains the wrapper name.
The purpose of this to cancel CI for a branch if it got a new commits (so new CI started).
Docs:
https://docs.github.com/en/actions/learn-github-actions/contexts
https://docs.github.com/en/actions/using-jobs/using-concurrency#example-only-cancel-in-progress-jobs-or-runs-for-the-current-workflow