You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when working with the very popular Composer bin plugin to isolate your dependencies in a php and composer depenency manager context, the resulting file structure in your repo looks like
the number of entries grows with the number of dependencies managed via "Composer bin plugin".
things would get a lot easier if we could glob/wildcard patterns in the directory config. when glob/wildcard patterns would be supported our dependabot.conf could get simplified to
I too would like this feature, I was exploring the source code - looking to understand how this works. I noticed that allowing the directory to config option to support globbing would really make this much more powerful. Right now we have many repos that have to define an entry per directory, it would be much easier to specify a glob instead.
This isn't specific to the package manager and requires some deeper changes in the way dependabot fetches the repo contents to work. We've got some ideas around how this will also play into grouped updates.
when working with the very popular Composer bin plugin to isolate your dependencies in a php and composer depenency manager context, the resulting file structure in your repo looks like
this means for every dependency/tool I managed via the "Composer bin plugin" today, I need to configure a separate pattern in my
dependabot.conf
.in our usual projects this looks like
the number of entries grows with the number of dependencies managed via "Composer bin plugin".
things would get a lot easier if we could glob/wildcard patterns in the
directory
config. when glob/wildcard patterns would be supported ourdependabot.conf
could get simplified tosee the
directory: /vendor-bin/*/
line which would contain "all the magic".The text was updated successfully, but these errors were encountered: