When Dependabot creates a PR for a particular update, and that update happens on the target branch by other means (manual update, for example), Dependabot will not automatically recognize this and close the PR.
Commenting @dependabot rebase works in this case, the PR is recognized as being no longer necessary. This is, however, not a practical solution when a lot of PRs have been opened.
I've seen #3782 which is about automatically rebasing Dependabot PRs. This is, however, not exactly the same: I don't need the rebase per se, and it would be a waste of resources 🌱 to run the rebase and subsequent workflows for every push to the target branch.
#3782 also mentions that Dependabot Native would do an automatic rebase in case of merge conflicts for the PR. But, when the manual update and the PR update to the same version of a dependency, often there is no such merge conflict, since the relevant lines in the lockfile (yarn.lock, composer.lock, ...) are the same on the target and base branch.
Previous behavior in Dependabot Preview:
I have already migrated away from Dependabot Preview and so I cannot try it again, but I am relatively sure that Dependabot Preview would immediately notice pushes to the the target branch and react accordingly.
When Dependabot creates a PR for a particular update, and that update happens on the target branch by other means (manual update, for example), Dependabot will not automatically recognize this and close the PR.
Commenting
@dependabot rebaseworks in this case, the PR is recognized as being no longer necessary. This is, however, not a practical solution when a lot of PRs have been opened.I've seen #3782 which is about automatically rebasing Dependabot PRs. This is, however, not exactly the same: I don't need the rebase per se, and it would be a waste of resources 🌱 to run the rebase and subsequent workflows for every push to the target branch.
#3782 also mentions that Dependabot Native would do an automatic rebase in case of merge conflicts for the PR. But, when the manual update and the PR update to the same version of a dependency, often there is no such merge conflict, since the relevant lines in the lockfile (
yarn.lock,composer.lock, ...) are the same on the target and base branch.Previous behavior in Dependabot Preview:
I have already migrated away from Dependabot Preview and so I cannot try it again, but I am relatively sure that Dependabot Preview would immediately notice pushes to the the target branch and react accordingly.