From 090d1ded2085823729bc7d8ee2ba8c2c35852797 Mon Sep 17 00:00:00 2001 From: Amith Mohanan Date: Mon, 2 Jan 2023 11:51:03 +0530 Subject: [PATCH] actions(concurrency): fix typo "will be cancelled" implies default behaviour, although it is not. --- data/reusables/actions/actions-group-concurrency.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/data/reusables/actions/actions-group-concurrency.md b/data/reusables/actions/actions-group-concurrency.md index f2b384b2dd21..a5e7acad7d97 100644 --- a/data/reusables/actions/actions-group-concurrency.md +++ b/data/reusables/actions/actions-group-concurrency.md @@ -1,4 +1,6 @@ -When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. +When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. + +Any previously pending job or workflow in the concurrency group can be canceled. To cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. ### Examples: Using concurrency and the default behavior