From 2b9632313756287ac45504c3db7aab3592033221 Mon Sep 17 00:00:00 2001 From: osndok Date: Sun, 8 Feb 2026 03:08:05 +0000 Subject: [PATCH] Note differing default value for concurrency.cancel-in-progress (#337) Whereas this bit me pretty hard, and [I don't seem to be the only one](https://forum.gitea.com/t/job-stopping-on-new-push/8142), the least we could do is let people know. --------- Co-authored-by: Robert Hailey Reviewed-on: https://gitea.com/gitea/docs/pulls/337 Reviewed-by: Lunny Xiao Co-authored-by: osndok Co-committed-by: osndok --- docs/usage/actions/comparison.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/usage/actions/comparison.md b/docs/usage/actions/comparison.md index ac6f1163..59f27faf 100644 --- a/docs/usage/actions/comparison.md +++ b/docs/usage/actions/comparison.md @@ -100,6 +100,14 @@ Services steps don't have their own section in the job log user interface. ## Different behavior +### Concurrency + +As of v1.21.0, gitea behaves as if `concurrency.cancel-in-progress` is set to `true`. + +This means that newly-triggered workflows will pre-empt runs already in progress for previous triggers. + +See [PR #25716](https://github.com/go-gitea/gitea/pull/25716) for additional details. + ### Downloading actions Previously (Pre 1.21.0), `[actions].DEFAULT_ACTIONS_URL` defaulted to `https://gitea.com`.