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
{{ message }}
This repository has been archived by the owner on May 24, 2022. It is now read-only.
Sometimes someone new to dependabot PRs will update a file in its commit, without a way to undo that, so dependabot will go "sorry, someone else edited my files, I can't rebase anymore now" even though we don't care about whether or not it "can", just that it "does" =)
Would it be possible to add a new command like @dependabot force-rebase or @dependabot redo, to make it throw away any changes past its own and only redoing the dependency bump based on whatever master is right now?
The text was updated successfully, but these errors were encountered:
Thanks so much! The "redo" command is probably the better of the two, since that suggests a do-over rather than a rebase (which normally includes all changes made).
Took a little longer than I though but I've just shipped this as @dependabot recreate (I couldn't think of a perfect name for it, as recreate suggests that Dependabot would close the PR and open a new one, but I think that's closest to what's happening. If folks get confused I may change it so that it actually does close the PR and open a new one).
Sometimes someone new to dependabot PRs will update a file in its commit, without a way to undo that, so dependabot will go "sorry, someone else edited my files, I can't rebase anymore now" even though we don't care about whether or not it "can", just that it "does" =)
Would it be possible to add a new command like
@dependabot force-rebase
or@dependabot redo
, to make it throw away any changes past its own and only redoing the dependency bump based on whatever master is right now?The text was updated successfully, but these errors were encountered: