"[skip ci]" will not work if the same push contains non-"[skip ci]" commits #13939

New Issue

GiteaMirror · 2025-11-02T10:57:50-06:00

GiteaMirror commented

2025-11-02 10:57:50 -06:00

Originally created by @ghnp5 on GitHub (Jan 9, 2025).

Description

If I do:

Commit with "[skip ci]"
Push

It works as expected - any Actions that would trigger from this push won't start.

But, I've just done this (intentionally):

Commit 2 workflow yamls with "[skip ci]" in the message
Then, commit another workflow yaml without "[skip ci]", as I wanted only that workflow to run, from this push
Push both commits at the same time

The 3 workflows triggered at the same time.
In the Actions history, it shows the message from the commit that only changed the workflow I wanted to run.

This indicates to me that Actions doesn't look at each commit message, but at the message of the very last commit in that push.

Gitea Version

1.23.0

Operating System

Windows 11

How are you running Gitea?

Gitea and Actions Runner are running on Docker, on the same host.

Database

MySQL/MariaDB

Originally created by @ghnp5 on GitHub (Jan 9, 2025). ### Description If I do: 1) Commit with "[skip ci]" 2) Push It works as expected - any Actions that would trigger from this push won't start. But, I've just done this (intentionally): 1) Commit 2 workflow yamls with "[skip ci]" in the message 2) Then, commit another workflow yaml **without** "[skip ci]", as I wanted only that workflow to run, from this push 3) Push both commits at the same time The 3 workflows triggered at the same time. In the Actions history, it shows the message from the commit that only changed the workflow I wanted to run. This indicates to me that Actions doesn't look at each commit message, but at the message of the very last commit in that push. ### Gitea Version 1.23.0 ### Operating System Windows 11 ### How are you running Gitea? Gitea and Actions Runner are running on Docker, on the same host. ### Database MySQL/MariaDB

GiteaMirror added the topic/gitea-actions issue/not-a-bug labels 2025-11-02 10:57:50 -06:00

GiteaMirror closed this issue

2025-11-02 10:57:50 -06:00

GiteaMirror commented

2025-11-02 10:57:51 -06:00

@Zettat123 commented on GitHub (Jan 10, 2025):

This is not a bug, it's by design. The trigger is push, not commit, so Gitea will only compare files between the commit before the push and the latest commit pushed, instead of checking every commit.

I did some testing on GitHub, and it looks like GitHub does the same thing: when pushing multiple commits, it only looks at the last commit.

@Zettat123 commented on GitHub (Jan 10, 2025): This is not a bug, it's by design. The trigger is `push`, not `commit`, so Gitea will only compare files between the commit before the push and the latest commit pushed, instead of checking every commit. --- I did some testing on GitHub, and it looks like GitHub does the same thing: when pushing multiple commits, it only looks at the last commit.

GiteaMirror commented

2025-11-02 10:57:51 -06:00

@ghnp5 commented on GitHub (Jan 10, 2025):

Ah... ok, then!
Thank you very much for your response and testing :)

@ghnp5 commented on GitHub (Jan 10, 2025): Ah... ok, then! Thank you very much for your response and testing :)

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#13939