Support organizing workflows in directories #15935
Replies: 31 comments 6 replies
-
Really interested on this 💯 |
Beta Was this translation helpful? Give feedback.
-
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 😅 |
Beta Was this translation helpful? Give feedback.
-
Hi! Is there any plan to have this feature implemented? Really interested on it! |
Beta Was this translation helpful? Give feedback.
-
Yeah, this would be really helpful. Bigger monorepos quickly gets cluttered :) |
Beta Was this translation helpful? Give feedback.
-
We also need this feature implemented. |
Beta Was this translation helpful? Give feedback.
-
Would love to have this |
Beta Was this translation helpful? Give feedback.
-
Great suggestion |
Beta Was this translation helpful? Give feedback.
-
+1 to this. Looks like I'm going to have to have long messy "..yml" filenames and "/" workflow names for now... |
Beta Was this translation helpful? Give feedback.
-
Definitely! |
Beta Was this translation helpful? Give feedback.
-
i require this |
Beta Was this translation helpful? Give feedback.
-
This would be great - we have 45 currently. |
Beta Was this translation helpful? Give feedback.
-
+1 this would be extremely helpful! |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
+1 this feature would be extremely helpful |
Beta Was this translation helpful? Give feedback.
-
We have a large implementation of GitHub, and it is frustrating to even think all our yml files are piled on the root directory. |
Beta Was this translation helpful? Give feedback.
-
DO we have any updates on this? |
Beta Was this translation helpful? Give feedback.
-
+1 here, some for organisation would be great for this folder! |
Beta Was this translation helpful? Give feedback.
-
This is probably closer to a need than a nice to have |
Beta Was this translation helpful? Give feedback.
-
help GitHub! |
Beta Was this translation helpful? Give feedback.
-
Hey sorry for the quietness here, this is on our backlog but we have no timeline yet. The first thing we are going to ship is a search option for the workflow list - we are working out dates for this now. For this one - how would y'all want to see those folders behave between branches (in the context of the current Actions page)? |
Beta Was this translation helpful? Give feedback.
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
+1 - Even in file explorers when you have 20+, even 30+ workflows it can become a bit unmanageable. Even just giving us the ability to organise the file directory despite how its displayed in the UI is a step up! |
Beta Was this translation helpful? Give feedback.
-
Organized and clear UI display with folders is definitely a need. We have a repo that has so many workflows in it. Without this feature, we are now thinking of coming up with a naming convention so they workflows will look like categorized. It has been causing a lot of confusions to our devs. |
Beta Was this translation helpful? Give feedback.
-
+1 - really helpful feature if available |
Beta Was this translation helpful? Give feedback.
-
We get 118 worflows. We're so eager to see the feature happen |
Beta Was this translation helpful? Give feedback.
-
+1 please add this, the UI is difficult to work with and is making errors all to easy |
Beta Was this translation helpful? Give feedback.
-
It is a great and necessary feature to be implemented |
Beta Was this translation helpful? Give feedback.
-
Would love to have this feature! |
Beta Was this translation helpful? Give feedback.
-
Over two and a half years, and this feature is still pending. Any updates? It’s crucial for improving workflow organization |
Beta Was this translation helpful? Give feedback.
-
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 :)
Beta Was this translation helpful? Give feedback.
All reactions