Abandoning PRs does not work as expected with multiple updates in one repository
See original GitHub issueHello!
I like the new ‘Abandon outdated PRs’ feature but it seems like it doesn’t work well with monorepos that have multiple projects to update.
We notice that dependabot will create a PR to update a dependency in one project on our repo, but then immediately abandon it when it goes to the next package in the repo. Right now there are zero updates from dependabot. We don’t observe this behavior in repos that contain only one project to update.
Additional Information
- The affected repo contains multiple Dart / Flutter packages. We are using the
pub
package ecosystem in Dependabot. - We are using Dependabot for Azure Devops version 1.13.378
- Our monorepo also has no lock files included in source control, could this actually be the issue?
Issue Analytics
- State:
- Created 9 months ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
if you need to do PRs in several repositories to do one fea...
My rule of thumb is: if you need to do PRs in several repositories to do one features, you should probably merge the...
Read more >Issues · tinglesoftware/dependabot-azure-devops
Tools for updating dependencies in Azure DevOps repositories using https://dependabot.com ... Abandoning PRs does not work as expected with multiple update.
Read more >Branches, tags and PRs not being created - Git X-Modules
I'm using GitHub and branches, tags and pull requests that I create in my parent repository are not created in the connected modules....
Read more >Should I abandon my monorepo? : r/rust
I'm currently working on a kernel, and am making various no_std ... a setup where you never need to sync two PRs, multiple...
Read more >Releasing repositories form "other" people
We have currently multiple PRs pending which release packages from "other" people (new versions and/or into more ROS distros).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for reporting this. Indeed working in a mono repo wasn’t considered, especially for different ecosystems or different directories. An attempt to fix this was made in #447 but clearly there’s more scenarios. You can opt out using the new input in #448.
I will keep this issue open as other alternatives are looked into. Maybe other similar reports will provide more insight. Could even be a contribution.
#478 was only meant to solve #466 not this one. There’s still no viable fix or workaround for closing unwanted PRs when there are multiple updates in the same repository. Contributions are welcome.
As regards the title, you have a valid concern. Thanks for raising it, I will update.