Open
Description
I often ask people to rebase PRs to trigger new CI runs, and sometimes do it myself. Unfortunately, it's pretty easy to get it wrong and end up touching way too many files, causing way too many labels and reviewers being added. It's hard to recover from this state, both in terms of fixing the git history and getting rid of all the labels and reviewers. Cases I've noticed in the past day:
- [css-values] Add tests for basic min() / max() support wpt#10377 (comment)
- WebKit export of https://bugs.webkit.org/show_bug.cgi?id=190642 wpt#13606 (comment)
- WebKit export of https://bugs.webkit.org/show_bug.cgi?id=188189 wpt#14221 (comment)
- test POST navigation with Referrer-Policy wpt#14879 (comment)
Most PRs are created with the ability for other contributors to push to the branches. Therefore, it should be pretty straightforward to support a request like @wpt-pr-bot rebase
, causing the branch to be rebased and force pushed.
I would certainly use that, but it wouldn't fix the whole problem because you can only use it if you know it exists.
Metadata
Metadata
Assignees
Labels
No labels