-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support wildcard for actions packages #5137
Comments
Hi @fmeriaux - wildcard configurations are something on our radar, but there's a little bit of a lift involved in terms of our scheduler so I don't have an ETA on this right now. |
This appears to be a duplicate of: That one is more generic, and so when we actually implement we may need to re-open this more specific ticket to track the specific changes necessary to enable actions... but I think the user-facing changes are all at the config file layer and generic across ecosystems so for now let's centralize the conversation over there. If I'm wrong, please comment and we can reopen. |
Hello, it is not clear to me if |
Good question. We currently special case |
Actually to update composite actions in a mono-repo, we have to declare something like:
After some discussions (cf: #4178 (comment)), I think it could be interesting to manage wildcards for this kind of use.
The text was updated successfully, but these errors were encountered: