From 5e4cd3b57790d2f1bbb1b12dae3cee2f34830341 Mon Sep 17 00:00:00 2001 From: silverwind Date: Wed, 8 Apr 2026 23:08:20 +0000 Subject: [PATCH] Remove obsolete actions concurrency notes (#377) `concurrency` is fully supported as of v1.26 via https://github.com/go-gitea/gitea/pull/32751, so remove the unsupported entry and the different-behavior note. Closes #340 --- This PR was written with the help of Claude Opus 4.6 Reviewed-on: https://gitea.com/gitea/docs/pulls/377 Reviewed-by: Lunny Xiao Co-authored-by: silverwind Co-committed-by: silverwind --- docs/usage/actions/comparison.md | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/docs/usage/actions/comparison.md b/docs/usage/actions/comparison.md index d7d1d73a..024da652 100644 --- a/docs/usage/actions/comparison.md +++ b/docs/usage/actions/comparison.md @@ -26,13 +26,6 @@ Github Actions doesn't support that. https://docs.github.com/en/actions/using-wo ## Unsupported workflows syntax -### `concurrency` - -It's used to run a single job at a time. -See [Using concurrency](https://docs.github.com/en/actions/using-jobs/using-concurrency). - -It's ignored by Gitea Actions now. - ### `jobs..timeout-minutes` See [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes). @@ -94,14 +87,6 @@ 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. - ### Job token permissions (`permissions`) Gitea supports `permissions` and `jobs..permissions` to control the default `GITEA_TOKEN` permissions.