☂️ Eli Hooten

While I consider this High priority, it's a deceptive amount of work. We will need to dedicate meaningful time to testing and updating this functionality. In addition, there may even...

Hypothesis: There is no webhook that fires when a branch name is changed, so we likely have to sync branch names some other way. We likely need to determine when/how...

passing to @codecovdesign as we've done extensive discovery work around this idea in the past, could be useful to revisit and see if we want to take any action on...

> we want the coverage to be calculated solely based on the files in the PR diff. @kfbustam Full disclosure, PR base picking is a fairly niche feature that isn't...

@kfbustam thanks for the clarification, here. If you're dealing with a less than ideal testing / CI setup, I understand why you'd want to rely on base picking to find...

@kfbustam we've chatted a lot about this feature request internally, and I _think_ you don't actually need this feature at all. Hear me out: Today, in the codecov UI, if...

> Yes this would actually work for us! When you say "notify the user..." you mean we'll see it as an appended message to the https://about.codecov.io/product/feature/status-checks/ patch coverage item row...

piggybacking on @codecovdesign 's update to share a bit more context. In an earlier post we outlined several scenarios where we believed we could report coverage accurately. One of those...

Settings are available for the org from the Settings tab in the repo view. At minimum we should probably make it clearer in the dropdown by changing the text to...

This is a feature request, and a quite large one. As such, it will need to go through a product definition, scoping, and prioritization process. @rohan-at-sentry to take next steps...