"run-name:" not working within action to define the name of the run #14389

Closed
opened 2025-11-02 11:11:40 -06:00 by GiteaMirror · 9 comments
Owner

Originally created by @laitco on GitHub (Apr 19, 2025).

Description

Hi!

i dont now if it is a bug or Layer7. I cannot get it working to define a fixed run name like it is done within the blog "https://blog.gitea.com/hacking-on-gitea-actions/".

name: Gitea Actions Demo
run-name: ${{ gitea.actor }} is testing out Gitea Actions 🚀
on: [push]
jobs:

When i am adding run-name it is still showing the commit message.

Am i doing something wrong or can someone help?

Not reproducable in demo, because CI/CD.

Gitea Version

1.23.7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Linux

How are you running Gitea?

Docker

Database

SQLite

Originally created by @laitco on GitHub (Apr 19, 2025). ### Description Hi! i dont now if it is a bug or Layer7. I cannot get it working to define a fixed run name like it is done within the blog "https://blog.gitea.com/hacking-on-gitea-actions/". name: Gitea Actions Demo run-name: ${{ gitea.actor }} is testing out Gitea Actions 🚀 on: [push] jobs: When i am adding run-name it is still showing the commit message. Am i doing something wrong or can someone help? Not reproducable in demo, because CI/CD. ### Gitea Version 1.23.7 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Linux ### How are you running Gitea? Docker ### Database SQLite
GiteaMirror added the topic/gitea-actionsissue/needs-feedbacktype/bug labels 2025-11-02 11:11:40 -06:00
Author
Owner

@lunny commented on GitHub (Apr 24, 2025):

Can you reproduce it in https://demo.gitea.com ?

@lunny commented on GitHub (Apr 24, 2025): Can you reproduce it in https://demo.gitea.com ?
Author
Owner

@laitco commented on GitHub (Apr 24, 2025):

Hi @lunny!

Yes.

Test-Repo:
https://demo.gitea.com/laitco/run-name-issue

Screens:

Image

Image

Image

@laitco commented on GitHub (Apr 24, 2025): Hi @lunny! Yes. Test-Repo: https://demo.gitea.com/laitco/run-name-issue Screens: ![Image](https://github.com/user-attachments/assets/61abd162-a9e4-44de-9dc5-0ac86fdcb3bb) ![Image](https://github.com/user-attachments/assets/66b99b17-b929-4299-bf3e-77670cbbf39a) ![Image](https://github.com/user-attachments/assets/793afa67-8dd8-4456-ae23-4d5a996b9be1)
Author
Owner

@badhezi commented on GitHub (Apr 27, 2025):

From what I personally remember this used to work but for the life of me i can't get it to work locally.
I also don't see how this will ever work the way we currently handle the creation of an action job run.

0376c09fc2/services/actions/notifier_helper.go (L303)

@lunny / @Zettat123 I can take the implementation of this if this actually needs implementing.

To my understanding we need to modify this part of act code to include run-name

Also how do we go about expanding ${{ gitea.* }} variables in server?

thanks.

@badhezi commented on GitHub (Apr 27, 2025): From what I personally remember this used to work but for the life of me i can't get it to work locally. I also don't see how this will ever work the way we currently handle the creation of an action job run. https://github.com/go-gitea/gitea/blob/0376c09fc27d848dbac471b629c83fd7a231852b/services/actions/notifier_helper.go#L303 @lunny / @Zettat123 I can take the implementation of this if this actually needs implementing. To my understanding we need to modify [this part of act code](https://gitea.com/gitea/act/src/branch/main/pkg/jobparser/model.go#L12) to include run-name Also how do we go about expanding `${{ gitea.* }}` variables in server? thanks.
Author
Owner

@badhezi commented on GitHub (Apr 28, 2025):

Created a preliminary PR for this, would love to get feedback
https://github.com/go-gitea/gitea/pull/34301

@badhezi commented on GitHub (Apr 28, 2025): Created a preliminary PR for this, would love to get feedback https://github.com/go-gitea/gitea/pull/34301
Author
Owner

@badhezi commented on GitHub (May 1, 2025):

I believe this can be resolved soon, waiting for review on
https://gitea.com/gitea/act/pulls/137
and https://github.com/go-gitea/gitea/pull/34301
@lunny

@badhezi commented on GitHub (May 1, 2025): I believe this can be resolved soon, waiting for review on https://gitea.com/gitea/act/pulls/137 and https://github.com/go-gitea/gitea/pull/34301 @lunny
Author
Owner

@laitco commented on GitHub (May 13, 2025):

Is it fixed in the newest version because it was merged into main?

@laitco commented on GitHub (May 13, 2025): Is it fixed in the newest version because it was merged into main?
Author
Owner

@badhezi commented on GitHub (May 13, 2025):

@laitco no this is not fixed yet, the PR in this repo still needs to me merged, it's ready however. Waiting for review and feedback.

@badhezi commented on GitHub (May 13, 2025): @laitco no this is not fixed yet, the PR in this repo still needs to me merged, it's ready however. Waiting for review and feedback.
Author
Owner

@wxiaoguang commented on GitHub (May 20, 2025):

Fixed by Use run-name and evaluate workflow variables #34301 and can be closed?

@wxiaoguang commented on GitHub (May 20, 2025): Fixed by Use run-name and evaluate workflow variables #34301 and can be closed?
Author
Owner

@laitco commented on GitHub (May 20, 2025):

Can be closed. Will test when i will be released in stable.

@laitco commented on GitHub (May 20, 2025): Can be closed. Will test when i will be released in stable.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14389