Feature Request: Actions: Support externally defined configuration files #10758

Open
opened 2025-11-02 09:17:27 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @kbingham on GitHub (Apr 30, 2023).

Splitting out from the now closed #13539

Yup now I've been exploring more, I can see a separated repo for the workflows could be a very helpful way of doing this too. Then multiple repos (mirrors, forks, or separate repos for separate developers) can point to common workflow actions.

FWIW - Today I discovered gitlab can do this and it's all documented here:

Originally posted by @kbingham in https://github.com/go-gitea/gitea/issues/13539#issuecomment-1518219043

Originally created by @kbingham on GitHub (Apr 30, 2023). Splitting out from the now closed #13539 > Yup now I've been exploring more, I can see a separated repo for the workflows could be a very helpful way of doing this too. Then multiple repos (mirrors, forks, or separate repos for separate developers) can point to common workflow actions. FWIW - Today I discovered gitlab can do this and it's all documented here: - https://docs.gitlab.com/ee/ci/pipelines/settings.html#specify-a-custom-cicd-configuration-file - https://gitlab.com/gitlab-org/gitlab/-/issues/14376 _Originally posted by @kbingham in https://github.com/go-gitea/gitea/issues/13539#issuecomment-1518219043_
GiteaMirror added the topic/gitea-actionstype/proposal labels 2025-11-02 09:17:27 -06:00
Author
Owner

@wolfogre commented on GitHub (May 4, 2023):

I think reusing workflows can do the same thing.

BTW, act runner supports reusing workflows, but there are some bugs in some cases.

@wolfogre commented on GitHub (May 4, 2023): I think [reusing workflows](https://docs.github.com/en/actions/using-workflows/reusing-workflows) can do the same thing. BTW, act runner supports reusing workflows, but there are some bugs in some cases.
Author
Owner

@kbingham commented on GitHub (May 4, 2023):

The problem I can see with reusable workflows is : https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow

The use case here means I can not add any specific CI files to the repository itself which is to be compiled. Specifically this is to support building libcamera and the linux kernel.

I can't merge my CI files into the linux kernel, and I'm not allowed to merge my CI files into libcamera.

@kbingham commented on GitHub (May 4, 2023): The problem I can see with reusable workflows is : https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow The use case here means I can not add any specific CI files to the repository itself which is to be compiled. Specifically this is to support building libcamera and the linux kernel. I can't merge my CI files into the linux kernel, and I'm not allowed to merge my CI files into libcamera.
Author
Owner

@Hypnotist1148 commented on GitHub (Oct 4, 2023):

Agree, being able to select common/shared configuration in the existing actions setting for a repository or even a whole organization would be a huge plus, especially for mirrors or for environments where Organizations and Repositories are managed by automated systems.
Or even just small teams.

@Hypnotist1148 commented on GitHub (Oct 4, 2023): Agree, being able to select common/shared configuration in the existing actions setting for a repository or even a whole organization would be a huge plus, especially for mirrors or for environments where Organizations and Repositories are managed by automated systems. Or even just small teams.
Author
Owner

@sthomen commented on GitHub (Jun 5, 2024):

I for one would very much prefer to not have to have configuration of the server leak into my code repositories.

@sthomen commented on GitHub (Jun 5, 2024): I for one would very much prefer to not have to have _configuration of the server_ leak into my code repositories.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10758