Optionally replace previous commits on the same branch

[tniessen]

We use this action in https://github.com/nodejs/node to create PRs with dependency updates. Sometimes, a new version of a dependency is released while the PR is still open, causing this action to (correctly) update the PR branch, title, and description. This happened, for example, in nodejs/node#46502 (except for updating the title and description, see nodejs/node#47621).

However, I haven't found a way of replacing previous commits on the branch instead of adding to them. In nodejs/node#46502, this meant that the action created one commit to update undici to 5.17.1 and then a separate commit to update undici to 5.18.0. It would be great to have an option to skip pulling in existing commits from the existing branch before force-pushing, i.e., in this case, it would have been great to be able to automatically skip the commit updating undici to 5.17.1 and to only keep the commit updating to 5.18.0.

[gr2m]

We use this action in https://github.com/nodejs/node to create PRs with dependency updates

woah cool! Thank you for letting me know!

I'd happily accept a pull request with a test. I can't work on it myself I'm afraid