dependabot / dependabot/dependabot-core
Reuse an open PR when updating a dependency instead of superseding it
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 1.5k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 149
Description
Hi guys,
I think that when there's a new bump release on a package that has an already opened PR, you can just upgrade that PR avoiding to open a new one.
Let's see this history, that happened in just 3 days:
Bump webpack from 4.1.1 to 4.6.0 https://github.com/chrvadala/react-svg-pan-zoom/pull/99
Superseded by https://github.com/chrvadala/react-svg-pan-zoom/pull/101
Bump webpack from 4.1.1 to 4.7.0 https://github.com/chrvadala/react-svg-pan-zoom/pull/101
Superseded by https://github.com/chrvadala/react-svg-pan-zoom/pull/106
Bump webpack from 4.1.1 to 4.8.1 https://github.com/chrvadala/react-svg-pan-zoom/pull/106
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing how Dependabot handles a newer release while an update pull request is open, using the webpack examples as the reproduction history; done means the existing pull request is updated rather than superseded by another one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, webpack
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100