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

[jacksgt]

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

[jacksgt]

I believe the check should be implemented here:

gitea/modules/actions/workflows.go

Line 211 in 79394b3

func matchPushEvent(commit *git.Commit, pushPayload *api.PushPayload, evt *jobparser.Event) bool {

[jacksgt]

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: #28020 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[JhonyGabriel]

@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.

[denyskon]

@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