Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@schalkms
Copy link
Member

The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493

The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493
@arturbosch
Copy link
Member

What's the reasoning behind reopening this?
Due to not writing duplicated tests for BindingContext.empty?

@schalkms
Copy link
Member Author

I didn't reopen the PR. I created a new one with a different codecov configuration.
Let's say we want to merge a PR, where the code coverage slightly goes down, into master.
This happened in 7187493. The build in the feature branch failed, because the code coverage went down. However, we don't want to fail the build on master too, if we decide to merge this feature branch resulting in a slightly lower coverage.

@arturbosch arturbosch merged commit ee93bf7 into detekt:master Sep 16, 2019
@arturbosch arturbosch added this to the 1.0.2 milestone Sep 16, 2019
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Sep 17, 2019
The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493
sowmyav24 pushed a commit to sowmyav24/detekt that referenced this pull request Sep 17, 2019
The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493
@arturbosch arturbosch modified the milestones: 1.0.2, 1.1.0 Sep 17, 2019
@schalkms schalkms deleted the codecov-fail branch November 8, 2019 18:11
smyachenkov pushed a commit to smyachenkov/detekt that referenced this pull request Dec 9, 2019
The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493
smyachenkov pushed a commit to smyachenkov/detekt that referenced this pull request Dec 9, 2019
The build on master shouldn't fail if the test coverage drops slightly.
See commit: 7187493
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants