actions push event was not triggered when it combines with workflow_call event #13975

Open
opened 2025-11-02 10:58:55 -06:00 by GiteaMirror · 9 comments
Owner

Originally created by @yougg on GitHub (Jan 13, 2025).

Description

it can reproduces on gitea demo:
https://demo.gitea.com/yougg/actions-demo/actions

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Debian 12

How are you running Gitea?

docker gitea with normal act_runner

Database

None

Originally created by @yougg on GitHub (Jan 13, 2025). ### Description it can reproduces on gitea demo: https://demo.gitea.com/yougg/actions-demo/actions ### Gitea Version 1.22.3 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Debian 12 ### How are you running Gitea? docker gitea with normal act_runner ### Database None
GiteaMirror added the topic/gitea-actionstype/bug labels 2025-11-02 10:58:55 -06:00
Author
Owner

@yp05327 commented on GitHub (Jan 14, 2025):

I can see a record in https://demo.gitea.com/yougg/actions-demo/actions/runs/1
image

What is the issue?

@yp05327 commented on GitHub (Jan 14, 2025): I can see a record in https://demo.gitea.com/yougg/actions-demo/actions/runs/1 ![image](https://github.com/user-attachments/assets/6132fcd7-f945-46a9-af82-417ee0e95737) What is the issue?
Author
Owner

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

I can see a record in https://demo.gitea.com/yougg/actions-demo/actions/runs/1 image

What is the issue?

I think the problem is that the release.yaml was supposed to be triggered by pushing a tag, but it wasn't.

https://demo.gitea.com/yougg/actions-demo/actions?workflow=release.yaml&actor=0&status=0

@Zettat123 commented on GitHub (Jan 14, 2025): > I can see a record in https://demo.gitea.com/yougg/actions-demo/actions/runs/1 ![image](https://private-user-images.githubusercontent.com/18380374/402839637-6132fcd7-f945-46a9-af82-417ee0e95737.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzY4NDE3OTQsIm5iZiI6MTczNjg0MTQ5NCwicGF0aCI6Ii8xODM4MDM3NC80MDI4Mzk2MzctNjEzMmZjZDctZjk0NS00NmE5LWFmODItNDE3ZWUwZTk1NzM3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAxMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMTE0VDA3NTgxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTYxMDM3YmQ3ZjI1NmMxMzE4N2MzZWEwNjBkMzkzZWRiMjdhOWU1ZjFkY2FlMTVlYWJmMjE2MDExMTU0MzkyNmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.mMAoD39ufgCzBy3765Vh0NJUatk_p5M6YoqwCVfPgoY) > > What is the issue? I think the problem is that the `release.yaml` was supposed to be triggered by pushing a tag, but it wasn't. https://demo.gitea.com/yougg/actions-demo/actions?workflow=release.yaml&actor=0&status=0
Author
Owner

@yp05327 commented on GitHub (Jan 14, 2025):

image
It can be triggered in my local environment which is using the main branch.


Edited:
https://demo.gitea.com/yp05327/testaction/actions
A same repo, but can be triggered in demo site. I created the files from the web side, not sure whether this is related.

@yp05327 commented on GitHub (Jan 14, 2025): ![image](https://github.com/user-attachments/assets/bf1e6d7d-fc9e-4999-9edf-a3462708dd77) It can be triggered in my local environment which is using the main branch. ------------ Edited: https://demo.gitea.com/yp05327/testaction/actions A same repo, but can be triggered in demo site. I created the files from the web side, not sure whether this is related.
Author
Owner

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

Same as yp05327's result.
https://demo.gitea.com/Zettat123/tag-workflow-call/actions


@yougg We cannot reproduce this issue on the demo site. Can you test it again?

@Zettat123 commented on GitHub (Jan 14, 2025): Same as yp05327's result. https://demo.gitea.com/Zettat123/tag-workflow-call/actions --- @yougg We cannot reproduce this issue on the demo site. Can you test it again?
Author
Owner

@yougg commented on GitHub (Jan 14, 2025):

try again on demo site but it can not be reproduced

@yougg commented on GitHub (Jan 14, 2025): try again on demo site but it can not be reproduced
Author
Owner

@yp05327 commented on GitHub (Jan 14, 2025):

Not sure about what happened, maybe it is already fixed? Or it is a random issue?
When did you create the orign demo repo?

@yp05327 commented on GitHub (Jan 14, 2025): Not sure about what happened, maybe it is already fixed? Or it is a random issue? When did you create the orign demo repo?
Author
Owner

@yougg commented on GitHub (Jan 14, 2025):

yesterday same as the commit time
2025年1月13日 GMT+8 下午2:31

@yougg commented on GitHub (Jan 14, 2025): yesterday same as the commit time 2025年1月13日 GMT+8 下午2:31
Author
Owner

@yougg commented on GitHub (Jan 14, 2025):

it can always reproduce on my local gitea server 1.22.3

@yougg commented on GitHub (Jan 14, 2025): it can always reproduce on my local gitea server 1.22.3
Author
Owner

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

I cannot reproduce it on v1.22.3

@Zettat123 commented on GitHub (Jan 16, 2025): I cannot reproduce it on v1.22.3
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13975