dependabot / dependabot/dependabot-core
Multi ecosystem groups problem with rebase and recreate
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 1.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 149
Description
Is there an existing issue for this?
- I have searched the existing issues
Package ecosystem
docker, github-actions, pip
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
multi-ecosystem-groups:
infrastructure:
schedule:
interval: "weekly"
commit-message:
prefix: ⬆
updates:
- package-ecosystem: "docker"
directory: "/"
multi-ecosystem-group: "infrastructure"
patterns: ['*']
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: weekly
groups:
python-packages:
patterns:
- "*"
commit-message:
prefix: ⬆
- package-ecosystem: "github-actions"
directory: "/"
multi-ecosystem-group: "infrastructure"
patterns: ['*']
Updated dependency
No response
What you expected to see, versus what you actually saw
When created a PR for infrastructure group we have gotten into a problem where recreate and rebase commands became buggy
You can see that ⚠️ Dependabot is rebasing this PR ⚠️ also stuck in the PR description I have Also tried to remove that part from PR desc. but nothing changed
but everything was OK when we had no multi-ecosystem group
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
https://github.com/openebs/rawfile-localpv/pull/202
Smallest manifest that reproduces the issue
version: 2
multi-ecosystem-groups:
infrastructure:
schedule:
interval: "weekly"
commit-message:
prefix: ⬆
updates:
- package-ecosystem: "docker"
directory: "/"
multi-ecosystem-group: "infrastructure"
patterns: ['*']
- package-ecosystem: "github-actions"
directory: "/"
multi-ecosystem-group: "infrastructure"
patterns: ['*']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal dependabot.yml configuration in the issue and reproduce the infrastructure group's behavior using the recreate and rebase commands. Then inspect the linked pull request https://github.com/openebs/rawfile-localpv/pull/202 for the stuck rebase message and expected behavior. Done means grouped Docker and GitHub Actions updates can be rebased or recreated without leaving the PR in a rebasing state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100