-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help contributors rebase PR branches #81
Comments
A trivial case to show what this looks like in practice: web-platform-tests/wpt#10571 (comment) |
This was referenced Oct 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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.
The text was updated successfully, but these errors were encountered: