Skip to content

Including tests+docs in sizing discourages both #9

@glb

Description

@glb

I’ve found on multiple occasions that adding unit tests or docs to a PR (or a PR that’s literally just unit tests) almost instantly bumps the PR into needing a +2 because of the size.

While the team is awesome about this, it seems like this almost discourages writing docs and tests.

I doubt there’s any appetite for changing how the bot does its calculations, but I thought I’d raise the topic in the hopes that maybe someone could educate me as to the benefits / rationale for the current method, or maybe it would stimulate some conversation about alternate strategies.

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions