Improve execution of reusable workflows #11347

New Issue

GiteaMirror · 2025-11-02T09:34:58-06:00

GiteaMirror commented

2025-11-02 09:34:58 -06:00

Originally created by @pmandalka on GitHub (Jul 27, 2023).

Feature Description

I try to create some reusable workflows. After some try and errors, I get the workflow to run as expected.
First, I was very confused about the UI in the run:

because my reusable workflow has multiple steps.

So I expected to see something like that:

It seems that the output of every step is in the "Set up job" step, e.g. you can see the "printenv"-step when it's started, it's output (truncated) and if it was successful.

Maybe I missed something - if not, this would be a nice feature to better support reusable workflows.

Screenshots

No response

Originally created by @pmandalka on GitHub (Jul 27, 2023). ### Feature Description I try to create some reusable workflows. After some try and errors, I get the workflow to run as expected. First, I was very confused about the UI in the run: ![image](https://github.com/go-gitea/gitea/assets/93120661/6bd09b1a-2c3d-4a1b-a17e-8fcbdec6d591) because my reusable workflow has multiple steps. ![image](https://github.com/go-gitea/gitea/assets/93120661/1c25f662-fa55-48f8-a771-6433ac2e2f06) So I expected to see something like that: ![image](https://github.com/go-gitea/gitea/assets/93120661/4f3d41dc-00fc-40f0-98d4-98a5cee269af) It seems that the output of every step is in the "Set up job" step, e.g. you can see the "printenv"-step when it's started, it's output (truncated) and if it was successful. ![image](https://github.com/go-gitea/gitea/assets/93120661/1752cace-d16b-40a6-9826-65ca7eb0501d) Maybe I missed something - if not, this would be a nice feature to better support reusable workflows. ### Screenshots _No response_

GiteaMirror added the topic/gitea-actions type/proposal labels 2025-11-02 09:34:58 -06:00

GiteaMirror commented

2025-11-02 09:34:58 -06:00

@wolfogre commented on GitHub (Jul 28, 2023):

Related to #24604

@wolfogre commented on GitHub (Jul 28, 2023): Related to #24604

GiteaMirror commented

2025-11-02 09:34:58 -06:00

@Sharaf5 commented on GitHub (Jun 21, 2024):

any update for this one

@Sharaf5 commented on GitHub (Jun 21, 2024): any update for this one

GiteaMirror commented

2025-11-02 09:34:58 -06:00

@dhofstetter commented on GitHub (Sep 29, 2024):

hello everybody,
is this considered as being an error?

Because I encountered the same behavior when designing my workflow using reusable workflow techniques and was curious (I mean maybe there is a good reason that it is as it is?)

BR Daniel

@dhofstetter commented on GitHub (Sep 29, 2024): hello everybody, is this considered as being an error? Because I encountered the same behavior when designing my workflow using reusable workflow techniques and was curious (I mean maybe there is a good reason that it is as it is?) BR Daniel

GiteaMirror commented

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

@jlbribeiro commented on GitHub (Sep 30, 2024):

@dhofstetter

hello everybody, is this considered as being an error?

Check #24604 for the reason why this happens, as well as a proposed solution/approach..

@jlbribeiro commented on GitHub (Sep 30, 2024): @dhofstetter > hello everybody, is this considered as being an error? Check #24604 for the reason why this happens, as well as a proposed solution/approach..

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