Skip to content

Feature: make configurable status check on coverage drop or add a kind of "tollerance" #84

@kmos

Description

@kmos

Hi,

First, thanks a lot for your work in this plugin, it's very useful for my organization even if code coverage reporting is a stressful topic.

I noticed that from version 2.1.1, is present the possibility to

Fail the status check when the coverage decreased

which is great and a fair point of discussion for the proposed code in PR but sometimes the report show something like that:

9695c93b-4837-4f9c-9e21-f88660ff1e75

which generate a bit of confusion and some awful discussion. I think that the reported value is truncated but the status check is evaluated with the complete value. Maybe a solution could be:

  • evaluate the status with the same value reported in the PR
  • add the possibility to disable the commit status or configure a tollerance value in which the status check is successful or failed.

Again thanks a lot for your work!

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