chore: added concurrency group to the pr workflow to automatically cancel previous workflow #2066
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RabiyaF
force-pushed
the
add-concurrency-group-to-pr-workflow
branch
from
3198932 to
f572fce
Compare
RabiyaF
changed the title
RabiyaF
force-pushed
the
add-concurrency-group-to-pr-workflow
branch
from
c319b6a to
f572fce
Compare
RabiyaF
force-pushed
the
add-concurrency-group-to-pr-workflow
branch
3 times, most recently
from
e45e0ec to
7c0d266
Compare
RabiyaF
force-pushed
the
add-concurrency-group-to-pr-workflow
branch
from
26b42a1 to
37876e1
Compare
RabiyaF
force-pushed
the
add-concurrency-group-to-pr-workflow
branch
from
83508cd to
37876e1
Compare
|
I tried updating the Windows workflow by using But what I added in this PR is the concurrency group and that is working fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is supposed to be another update for sustainability and optimising resources. I noticed when I pushed two subsequent changes, the previous workflow keep running. As can be seen in the actions list below.
I have added concurrency to
pr.ymlto stop the previous workflow.I have tested it as well and it work fine. This can be verified from the the actions list.
The workflow associated with the latest commit will run and jobs from the previous commit will automatically be cancelled.
