You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally a user will manually update (or remove) dependencies that deps has already created PRs for. If this happens, deps ci should know how to close the PR and delete the branch automatically.
For now, this behavior should only apply if dependency "types" aren't specified (i.e. deps ci vs deps ci --type python), so that we don't have to worry about accidentally closing PRs for another type than what is currently being processed:
We'll basically be adding a new concept of "irrelevant updates" (suggestions for what to call this are welcome, but we already use "outdated" for updates that can be re-updated):
Occasionally a user will manually update (or remove) dependencies that deps has already created PRs for. If this happens,
deps ci
should know how to close the PR and delete the branch automatically.For now, this behavior should only apply if dependency "types" aren't specified (i.e.
deps ci
vsdeps ci --type python
), so that we don't have to worry about accidentally closing PRs for another type than what is currently being processed:deps/internal/runner/ci.go
Line 22 in d8867cf
We'll basically be adding a new concept of "irrelevant updates" (suggestions for what to call this are welcome, but we already use "outdated" for updates that can be re-updated):
deps/internal/runner/ci.go
Lines 89 to 91 in d8867cf
We should be able to figure out which updates are "irrelevant" by finding all branches that belong to deps, and then finding those that we don't have a new/outdated/existing update for. The PRs can then be found matching the branch names, closed, and the branches deleted.
To start, this feature can be selectively enabled for GitHub. GItLab and Bitbucket support can be added later.
This is a bigger project so please ask questions if you have them!
This RFW is currently worth $500 and you'll be paid when we merge your PR. You can find more information and other RFWs on the Dropseed website.
Any questions can be asked here or through our private contact page!
The text was updated successfully, but these errors were encountered: