Support organizing workflows in directories

[AvivPeledTalon]

As it currently stands, all workflows have to be in the .github/workflows directory.
We currently have around 30 workflows, and that number increases as time goes.
We also have specific workflows for specific platforms (Win/Mac/Linux etc.) and as we support more platforms, the number of workflows multiplies.

It is getting to the point where it's hard to pick the correct workflow to run from the list, and it's getting messy to maintain.

I would have loved it if I could at least organize my workflows by platform i.e having .github/workflows/win for the windows workflows etc.

I know that this change as is requires a significant UI modification, but I think it's supposed to be pretty straightforward to at least allow reusable workflows to exist in subdirectories of the workflows dir (since we specify a full path when using them) - I might be wrong though.

I would appreciate it if you consider this :)

[sergio-toro]

Really interested on this 💯

[worace]

Also interested in this. Currently have about 12 files in our workflows dir and we haven't even finished migrating the remaining (bulk) of our CI config off of CircleCI. Probably will end up with like 40-50 yaml files in this flat directory in the end.

Especially frustrating since not all workflows are the same -- some of them will be "entrypoint" workflows configuring actual runs, while others are meant as "library" (reusable) workflows to be called by other workflows programmatically. It's surprising to me that Github just requires you to pile all of these into a single flat directory.

Have people discovered any other helpful techniques to organize large numbers of workflows in these directories?

On the one hand, we should count ourselves lucky, since at least GH lets you split them into separate files, unlike Circle which requires just 1 giant yaml file. But sheesh 😅

[carolinapc]

Hi! Is there any plan to have this feature implemented? Really interested on it!
@worace we have being prefixed the names of the workflows by category, so we can organized them and be easier to find what is dispatch, reusable, schedule jobs, etc. But would be nice if we can organize them in folders.

[robertherber]

Yeah, this would be really helpful. Bigger monorepos quickly gets cluttered :)

[ashish5bista]

We also need this feature implemented.

[davidvc]

Would love to have this

[rbeucher]

Great suggestion

[Tiger-Tom]

+1 to this. Looks like I'm going to have to have long messy "..yml" filenames and "/" workflow names for now...

[mateustalles]

Definitely!

[hudsonm62]

i require this

[JHooper-bsl]

This would be great - we have 45 currently.

[cwalker-vizio]

+1 this would be extremely helpful!

[ShahryarSaljoughi]

It's shocking that the request has not received a response in almost two years! It would be better if you had provided clarification on whether the issue is planned for the future, or if it is not a priority and won't be addressed anytime soon.

[dannymorris]

+1 this feature would be extremely helpful

[shanchatterjee]

We have a large implementation of GitHub, and it is frustrating to even think all our yml files are piled on the root directory.
GitHub should really think of folder management.
Azure DevOps is perfect, we might move there soon.

[ToxicBakery]

Actions + monorepos really need some better support. If we could add a group name to workflows or, as suggested, leverage directories to organize actions it would be immensely helpful for large repositories.