Skip to content
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

Closed
fmeriaux opened this issue May 13, 2022 · 4 comments
Closed

Support wildcard for actions packages #5137

fmeriaux opened this issue May 13, 2022 · 4 comments
Labels

Comments

@fmeriaux
Copy link

Actually to update composite actions in a mono-repo, we have to declare something like:

version: 2
updates:
  # Maintain dependencies for GitHub Actions (/.github/workflows)
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"

  - package-ecosystem: "github-actions"
    directory: "/actions/<my-custom-action-A>"
    schedule:
      interval: "daily"

  - package-ecosystem: "github-actions"
    directory: "/actions/<my-custom-action-B>"
    schedule:
      interval: "daily"

After some discussions (cf: #4178 (comment)), I think it could be interesting to manage wildcards for this kind of use.

version: 2
updates:
  # Maintain dependencies for GitHub Actions (/.github/workflows)
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"

  - package-ecosystem: "github-actions"
    directory: "/actions/**"
    schedule:
      interval: "daily"
@brrygrdn
Copy link
Contributor

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.

@jeffwidman
Copy link
Member

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.

@jeffwidman jeffwidman closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2023
@nikaro
Copy link

nikaro commented Feb 23, 2023

Hello, it is not clear to me if directory: "/actions/**" will look into .github/actions/ or into actions/ at the root of the repo. Can someone enlight me? 🙏

@deivid-rodriguez
Copy link
Contributor

Good question. We currently special case / to also look at .github/workflows but other than that, any directory configuration set looks exactly where instructed. So it should be actions/ at the root of the repo I believe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants