Skip to content

Help contributors rebase PR branches #81

Open
@foolip

Description

@foolip

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions