Support skipping Gitea Action workflows [ci skip] [no ci] ... #11997

New Issue

GiteaMirror · 2025-11-02T09:53:57-06:00

GiteaMirror commented

2025-11-02 09:53:57 -06:00

Originally created by @jacksgt on GitHub (Nov 13, 2023).

Description

Hello, thanks everyone for the awesome Gitea Actions feature!

GitHub Actions (and many other CI tools, too) has a feature that allows the user to skip running CI when a particular keyword is part of the commit message.
GitHub documentation: https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs

You can skip workflow runs triggered by the push and pull_request events by including a command in your commit message:
[skip ci]
[ci skip]
[no ci]
[skip actions]
[actions skip]

It seems that this is currently not supported by Gitea (can anyone else confirm this?).
Short term, it should be added to the list of Unsupported features: https://docs.gitea.com/next/usage/actions/comparison
Medium term we should of course implement this feature.

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

Gitea Helm chart version 9.5.1: https://gitea.com/gitea/helm-chart/

Database

MySQL/MariaDB

Originally created by @jacksgt on GitHub (Nov 13, 2023). ### Description Hello, thanks everyone for the awesome Gitea Actions feature! GitHub Actions (and many other CI tools, too) has a feature that allows the user to skip running CI when a particular keyword is part of the commit message. GitHub documentation: https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs > You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message: > [skip ci] > [ci skip] > [no ci] > [skip actions] > [actions skip] It seems that this is currently not supported by Gitea (can anyone else confirm this?). Short term, it should be added to the list of Unsupported features: https://docs.gitea.com/next/usage/actions/comparison Medium term we should of course implement this feature. ### Gitea Version 1.20.5 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots ![Screenshot 2023-11-13 at 16-56-33 blog](https://github.com/go-gitea/gitea/assets/11589682/69b1f5ee-aa7f-4a7c-aeb4-8a31a02d31ee) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Gitea Helm chart version 9.5.1: https://gitea.com/gitea/helm-chart/ ### Database MySQL/MariaDB

GiteaMirror added the topic/gitea-actions type/enhancement labels 2025-11-02 09:53:57 -06:00

GiteaMirror closed this issue

2025-11-02 09:53:57 -06:00

GiteaMirror commented

2025-11-02 09:53:59 -06:00

@jacksgt commented on GitHub (Nov 15, 2023):

I believe the check should be implemented here: 79394b340d/modules/actions/workflows.go (L211)

@jacksgt commented on GitHub (Nov 15, 2023): I believe the check should be implemented here: https://github.com/go-gitea/gitea/blob/79394b340d227182f94bae48cb08a091c78f2ea2/modules/actions/workflows.go#L211

GiteaMirror commented

2025-11-02 09:53:59 -06:00

@jacksgt commented on GitHub (Nov 18, 2023):

My gosh, that was fast! Many thanks!

On November 18, 2023 12:37:21 PM GMT+01:00, Lauris BH @.***> wrote:

Closed #28020 as completed via #28075.

--
Reply to this email directly or view it on GitHub:
https://github.com/go-gitea/gitea/issues/28020#event-11001585394
You are receiving this because you authored the thread.

Message ID: @.***>

@jacksgt commented on GitHub (Nov 18, 2023): My gosh, that was fast! Many thanks! On November 18, 2023 12:37:21 PM GMT+01:00, Lauris BH ***@***.***> wrote: >Closed #28020 as completed via #28075. > >-- >Reply to this email directly or view it on GitHub: >https://github.com/go-gitea/gitea/issues/28020#event-11001585394 >You are receiving this because you authored the thread. > >Message ID: ***@***.***>

GiteaMirror commented

2025-11-02 09:53:59 -06:00

@JhonyGabriel commented on GitHub (Nov 22, 2023):

@lunny, following the thread, in my workflows,
at version 1.21, auto-cancellation of simultaneous jobs was implemented if the type event is push, like described in issue #25716. I would like to suggest that when using [ci skip] on the commit message, the running jobs will are not cancelled at all.

@JhonyGabriel commented on GitHub (Nov 22, 2023): @lunny, following the thread, in my workflows, at version 1.21, auto-cancellation of simultaneous jobs was implemented if the type event is push, like described in issue #25716. I would like to suggest that when using [ci skip] on the commit message, the running jobs will are not cancelled at all.

GiteaMirror commented

2025-11-02 09:54:00 -06:00

@denyskon commented on GitHub (Nov 22, 2023):

@JhonyGabriel It should already work that way. The skip ci check happens before the auto-cancellation, so running workflows are not being cancelled if there's a skip ci string in the commit

@denyskon commented on GitHub (Nov 22, 2023): @JhonyGabriel It should already work that way. The skip ci check happens before the auto-cancellation, so running workflows are not being cancelled if there's a skip ci string in the commit

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11997