service doesn't create PRs for the same dependency across multiple directories with wildcard

[lucacome]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Docker

Package manager version

No response

Language version

No response

Manifest location and content before the Dependabot update

No response

dependabot.yml content

https://github.com/opentracing-contrib/nginx-opentracing/blob/master/.github/dependabot.yml

Updated dependency

No response

What you expected to see, versus what you actually saw

Dependabot says this in the logs:

updater | 2024/06/26 23:45:12 INFO Results:
updater | +------------------------------------------+
updater | |   Changes to Dependabot Pull Requests    |
updater | +---------+--------------------------------+
updater | | created | ubuntu ( from 22.04 to 24.04 ) |
updater | | created | php ( from 7-fpm to 8-fpm )    |
updater | | created | ubuntu ( from 18.04 to 24.04 ) |
updater | | created | ubuntu ( from 18.04 to 24.04 ) |
updater | | created | ubuntu ( from 18.04 to 24.04 ) |
updater | | created | ubuntu ( from 17.10 to 24.04 ) |
updater | | created | ubuntu ( from 17.10 to 24.04 ) |
updater | | created | ubuntu ( from 22.04 to 24.04 ) |
updater | | created | python ( from 3.10 to 3.12 )   |
updater | +---------+--------------------------------+

but it only opened:

• one PR for ubuntu with only one file changed Bump ubuntu from 22.04 to 24.04 in /ci opentracing-contrib/nginx-opentracing#631
• one PR for php Bump php from 7-fpm to 8-fpm in /example/php/jaeger opentracing-contrib/nginx-opentracing#632 (this seems correct)
• one PR for python Bump python from 3.10 to 3.12 in /test/environment/grpc opentracing-contrib/nginx-opentracing#633 (this seems correct)

I expected a PR for ubuntu with changes to all the Dockerfiles

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response

[lucacome]

I triggered dependabot again after merging 631 and it opened one for the next ubuntu on the list
opentracing-contrib/nginx-opentracing#634
but then decided to supersede it with one in another folder
opentracing-contrib/nginx-opentracing#635

[rob-zz]

I'm seeing something similar with this config:

version: 2
updates:
  - package-ecosystem: "terraform"
    directories:
      - "*"
    schedule:
      interval: "monthly"

This is running on a Terraform project having multiple envs in multiple directories, with manifest files like this:

lab/providers.tf
acc/providers.tf
prd/providers.tf

It only creates a PR for one of the dirs/files.

[lucacome]

From the conversation in #2178 it seemed like using the grouping settings would force dependabot to open a PR with all the changes across multiple directories.

But this doesn't seem to be working either.

I have a grouping of go.opentelemetry.io/otel dependencies and dependabot opened just one PR for a single directory instead of two.

[deki]

@lucacome same behavior on my end

[anthonysomerset]

I'm seeing something similar with this config:

version: 2
updates:
  - package-ecosystem: "terraform"
    directories:
      - "*"
    schedule:
      interval: "monthly"

This is running on a Terraform project having multiple envs in multiple directories, with manifest files like this:

lab/providers.tf
acc/providers.tf
prd/providers.tf

It only creates a PR for one of the dirs/files.

i ran this same config, and then created seperate lines for individual directories thinking this was the issue but i get the same behaviour in both scenarios

EDIT

i was able to make this work with the following groups config:

    groups:
      minor-and-patch:
        update-types:
          - "patch"
          - "minor"

however not keen on the PR name that gets opened but it gets the job done:
Bump the minor-and-patch group across 8 directories with 1 update #6

for me i would love a grouping that bases on the directory with updates so 1 PR per folder