-
Notifications
You must be signed in to change notification settings - Fork 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
Spec multiple directories for one package-ecosystem #3951
Comments
It's currently not possible unfortunately @tobiasehlert, but it is on our radar. I can't commit to when we'll be able to look into it, but for some setups the config is a little painful currently :( I know some people have a little script that generates the config file for them, it's not ideal but it's an improvement. I can try to track down an example of such a script if it'd be useful. This seems like a combination of #649 or maybe #2178 and #1190 As the issues you describe are already tracked elsewhere, I'm going to close this out. |
Seems dependabot looks specifically for pom files named `pom.xml`. We therefore introduce an additional level of directories (named same as the alias.) Unfortunately, these means we'll need to edit `dependabot.yml` as we add and remove aliases. See: - dependabot/dependabot-core#3951 - dependabot/dependabot-core#2824
Hello,
I've a repo with around 50 directories where 25~ have a Terraform provider file specifying a provider version.
As it looks to me, I need to create a separate entry for every modules directory in dependabot.yaml, which results in a very long file. Or maybe that I would add /modules instead and that depedabot would go through all .tf files inside the directories recursively..
E.g. of 3 helm provider modules
This should be much more nice to do this with the 3 helm repos
Or maybe even better to be able to use it recursively like this..
And if one provider gets updated, the bump currently is done for every
-package-ecosystem
so with the combine of directories, it's maybe possible to get one PR for one provider bump and not multiple PRs for the same provider-bump?The text was updated successfully, but these errors were encountered: