Feature request: allow workflow configuration in sub-folders #18055
Replies: 71 comments 93 replies
-
I was searching for a way to organise many workflows in the UI, like by category or by team for a mono-repo. And I was thinking about just being able to create subfolders in the ./github/workflow/ folder, and that each folder would appear as a collapsable section in the UI. But this proposal would be even better, at least when it comes to separation of files, but I'm not sure how it would be presented in the UI? |
Beta Was this translation helpful? Give feedback.
-
I was trying to do:
With the hope that I would see a list of actions as
or something similar. Since the action names are configured in the yml files it would make sense to namespace actions according to the directory they are in. For my use case, aside from namespacing actions via a directory name, nothing would change (though since I use only a small subset of actions functionality I'm not sure if there are other considerations). It would be nice if it was possible to put In any case, thank you for the actions tooling! It's pretty amazing. |
Beta Was this translation helpful? Give feedback.
-
It would also be rather nice if there could be a way to run a workflow nested in a submodule, and then leverage that same submoduled workflow to work on the parent repository. This is definitely a much bigger ask than what the original discussion was most likely tailored for, but it would certainly come in use for a repository I currently maintain. |
Beta Was this translation helpful? Give feedback.
-
This will help a lot my team for a mono-repo! I hope to saw this feature soon |
Beta Was this translation helpful? Give feedback.
-
You can do a lot of this by using a It isn't perfect, but, you can do it. Or, you could just use Forcing GitHub to recurse through the entire tree, or even a large slice of a tree whenever it receives any event is almost certainly a non-starter. I appreciate the problem, but don't think that asking them to do this is likely to go anywhere. What you can do is have your workflow load its configuration from a file at a path in your chosen directory. Many public workflows do this, although typically that directory is |
Beta Was this translation helpful? Give feedback.
-
A good workaround is symbolic links in your root directory |
Beta Was this translation helpful? Give feedback.
-
This feature would be awesome to have for when using both re-usable workflows and the "regular" workflow. Right now, I'm naming things with emojis in front of them to do this. 😂 It gets a little ⚡ if it's a re-usable. |
Beta Was this translation helpful? Give feedback.
-
Apparently it doesn’t work
…On Tue, Aug 2, 2022 at 6:32 AM Tim Kretschmer ***@***.***> wrote:
How can i achieve this?
ln -s ?
—
Reply to this email directly, view it on GitHub
<#18055 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOE4LLF6VBUR4F74GVLKSLVXD2KHANCNFSM5YELZWBA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Instead of recursing through the whole repo, why not provide a keyword in the root .github/workflows that can be used to point to the "sub-root" of the directory you want to treat as it's own repo (for actions)? Something like this: In
In
Benefits:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
This would be a nice feature for our template projects, to make certain workflows optional and easy to tear out (with related scripts). eg. "Not using the event queue system? tear out the workflow and related integration testing scripts by pulling ONE folder..." Suggested workaround: strictly enforced naming conventions on the workflow files. e.g. " |
Beta Was this translation helpful? Give feedback.
-
also running a monorepo and having workflow subfolders would be great as we have a lot of granular separation going on. this would be ideal for us:
|
Beta Was this translation helpful? Give feedback.
-
I've been following this thread for a while, if you're interest I made a simple cli in rust that can help with workflows context separation. Is still a WIP, nothing fancy. Hope this helps someone ✌️ |
Beta Was this translation helpful? Give feedback.
-
Has there been any progress made on this? Being able to define a |
Beta Was this translation helpful? Give feedback.
-
We are using monorepo setup and our |
Beta Was this translation helpful? Give feedback.
-
Without this feature the real-world cases with a lot of microservices are close to unusable. Wondering why it's deprioritized that hard when it's clear that it affects user experience in a major way. |
Beta Was this translation helpful? Give feedback.
-
Hey y'all, sorry for being quiet on this. We are going to be trying to get through some of these long-standing paper cuts over the next 6-9 months (I am just looking at those that have been particularly active this week today :D ). This one is for sure on our list to consider. We did a small improvement in this space from the UI point of view (for those who didn't see) by adding pinning :) https://github.blog/changelog/2024-04-30-github-actions-ui-improvements/ But I appreciate given the scale of some of your repos/workflows this isn't going to cut it. Thank you all for taking the time to feedback and watch this space as we try and get some focus back onto these longer standing items <3 |
Beta Was this translation helpful? Give feedback.
-
Hey there from Actions 👋 To provide an update here, this is not something we have planned for this year. Just to set expectations, we will not be revisiting this until next calendar year. |
Beta Was this translation helpful? Give feedback.
-
Please prioritise this in upcoming releases, much needed feature. |
Beta Was this translation helpful? Give feedback.
-
I would really like the ability to use subdirectories in the .github/workflows/ directory. that would solve 95% of our issues. |
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.
-
I think I asked this on another of these, but anyone who has feedback on how you would like branches to work with a folder view would be <3 (especially if people are moving workflows between folders etc). |
Beta Was this translation helpful? Give feedback.
-
AFAIK to get workflows to show up in the web view in the first place, they have to be present in the default branch. I'd be ok with a version of this feature that only honored folder structure in that branch. |
Beta Was this translation helpful? Give feedback.
-
I have a different reason for wanting support for sub-directories (I couldn't care less about lookup of all .github directories in a repo though), e.g. |
Beta Was this translation helpful? Give feedback.
-
One more use case for folders is usage of README.md to document usage of workflow. Having documentation for all workflow in single readme is not ideal. |
Beta Was this translation helpful? Give feedback.
-
Copying this feature request over from https://github.saobby.my.eu.orgmunity/t/feature-request-allow-workflow-configuration-in-sub-folders/16776
Beta Was this translation helpful? Give feedback.
All reactions