Skip to content

Bot shouldn't mark large "problematic" PRs with needs_rebase / needs_revision #33

@tremble

Description

@tremble

There are a number of legitimate reasons why a PR will change more than 50 files (for example a release, or a new module using placebo for unit tests).

"needs_rebase" / "needs_revision" implies that a change must be made. It would be better to add a dedicated "large_patch" label.

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