GitHub Community
Support organizing workflows in directories #15935
Replies: 141 comments 28 replies
|
Really interested on this 💯 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
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 😅 |
|
Hi! Is there any plan to have this feature implemented? Really interested on it! |
|
Yeah, this would be really helpful. Bigger monorepos quickly gets cluttered :) |
|
We also need this feature implemented. |
|
Would love to have this |
|
Great suggestion |
|
+1 to this. Looks like I'm going to have to have long messy "..yml" filenames and "/" workflow names for now... |
|
Definitely! |
|
i require this |
|
This would be great - we have 45 currently. |
|
+1 this would be extremely helpful! |
|
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. |
|
3 years now |
|
+1 this feature would be extremely helpful |
|
We have a large implementation of GitHub, and it is frustrating to even think all our yml files are piled on the root directory. |
|
+1 |
|
We have the same issue. I have built a Chrome extension that allows to have a hierarchical view of your actions/workflows, given you use a naming convention for your workflow names. See https://chromewebstore.google.com/detail/github-workflow-navigator/fgjjlimpehmkbeeeiohhndjhjccndkpb to install and https://github.com/wimdeblauwe/github-workflow-navigator for the sources if you want to check it out. |
|
Crazy that 4 years later there isn't anything about this - at all. This would make our lives so much easier in managing reusable workflows across all of our repositories and its left in "Unanswered" state 500+ upvotes and 100+ comments, feels like many voices pleading into the void at this point. Between this and the fact you also can't organise your Github repositories into folders/directories, I have to wonder why the company is so adverse to the concept of folders, they've been a part of computing for as long as I can personally remember and yet they've became a feature that you can wait for over 4 years to receive any attention - for both ! |
|
Guys, update this already. |
|
It's a problem happening can we fix it. |
|
Apparently, MicroShaft is too busy excellifying GitHub to be bothered by a "few" disgruntled devs... |
|
Yeah I'm looking forward to checking out the details. |
|
+1, any chance this could be implemented? 🙂 |
|
+1 would really help! |
|
This would be very useful for larger repositories and monorepos. The current flat A folder structure would make workflows easier to scan and safer to maintain, for example:
This would especially help separate entrypoint workflows from reusable workflows. Right now both have to live in the same flat directory, so teams end up encoding structure into long filenames instead of using real organization. Even if GitHub still displayed all workflows in one Actions list, allowing subdirectories in the repository would already improve maintainability. A good minimal version could be:
This would reduce naming hacks, make large repositories easier to navigate, and help teams manage CI/CD at scale without relying only on filename conventions. |
|
GitHub team, please implement this! This will make the CI/CD infra better!! |
|
No answer whatso ever from Github? |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
+1 |
|
This is related, but if it requires its own issue I can make it, but could we allow searching workflows on the actions tab? Or group them by trigger, so I can see all my workflow_dispatch actions together? |
and others
Uh oh!
There was an error while loading. Please reload this page.
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 :)
All reactions