Including tests+docs in sizing discourages both

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?

Start by reviewing the pull-sizer bot's current size-calculation rules, specifically how unit tests and documentation changes are counted. Investigate the rationale for the current method and compare possible alternative strategies; the issue is done only when a concrete approach is agreed and specified.

Scritto dal modello di indicizzazione a partire dal testo della issue.