Actions: Better DX for Monorepos

[rawkode]

Feature Description

I have a monorepo and while it's not necessarily "bad" to put all my actions definitions in the root of the repository, my quality of life could be so much better if we could support nesting action files anywhere within the repository, where some inferences could be made about the actions:

• only run when changes made to the nested directory
• relative paths within action are relative from nested directory
• working directory is relative to nested directory

Screenshots

No response

[rawkode]

I got a prototype of this working on the Rawkode Academy Gitea

[rawkode]

@techknowlogick There doesn't appear to be a way to set the working directory for actions, is this a current limitation or have I just missed something?

[ChristopherHX]

There doesn't appear to be a way to set the working directory for actions,

In nektos/act perspective per emulating GitHub Actions this is old "undefined behavior" (until 1. September 2024) and no longer permitted to be triggered after schema validation has been added in the upstream project.

undefined per not forcefully stopped from being run and ignored for uses steps

[lunny]

A method is caching all the workflow file paths into database when pushing and you have to compare between the affected file path and the workflow directories.

.gitea/workflows is root directory, all files changes should trigger them.
a/.gitea/workflows is only for the changes in the directory a/.