Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions eng/codecov.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
codecov:
branch: master
ci:
- dnceng.visualstudio.com
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❔ Can you provide more information about what this does?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure: https://docs.codecov.io/docs/detecting-ci-services#section-detection-technique.

As we upload our reports from helix machines, the codecov's detection technique fails and can't figure out which CI service is used. We ideally should set this variable in the teams codecov yml but I don't permissions to do so: https://docs.codecov.io/docs/codecov-yaml#section-team-yaml


coverage:
range: 60...90
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❔ Can you describe the motivation behind this range? I always recommend that teams using code coverage tools never gate on a particular coverage number, but I can think of other reasons why this might be included. I'm curious why it's used here.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I lowered the lower bound temporarily as our coverage numbers aren't great for most of our libraries. As soon as codecov integration is enabled in corefx I will adjust these settings based on what makes sense.


comment:
layout: "reach, diff, files"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 reach is an impediment to mobile browsing and does not really provide a benefit. I recommend omitting files as well, though this can wait until some point in the future when you realize it's not especially helpful 😄

require_changes: yes