Codecov Product Design

@dogederp @albanh thank you for the feedback. We investigated this and realized the anchor of "GitHub Actions" was going to the wrong page (it's been fixed). Further, based on you're...

@jayber sorry for my delay, just noticing this. Thanks for the feedback. > What pull request? there are no pull requests. Do there need to be? No, it doesn't require...

> with: > token: ${{ secrets.CODECOV_TOKEN }} @gregorywilliams that's right, and we'll be adding this input to the repo guide page ✅ @philgyford I'm unsure what the issue is based...

@larryaasen @JohannLai @enraiha0307 thank you for raising the syntax error. The fix in live:

@Aerendir thank you for your feedback! Based on it, I'm creating some updates to the copy to be more clear in the documentation / setup guide 🙏 . > The...

@philgyford that is confusing and thanks for raising 🙏 . For the 1st and 3rd examples that is specific to GitHub actions and the 2nd input is generic for other...

@houserx-jmcc thank you for the feedback 🙏 > nice to set a threshold change to not trigger a comment I've added the update proposal to this WIP issue: https://github.com/codecov/engineering-team/issues/1350

@karl-sjogren thanks for the great feedback! 🙏 > some way to filter or split bundles when reporting From my understanding of your feedback, based on that I created this issue...

@TechMaz thank you for your feedback. We are actually experimenting with a new layout, see below. It prioritizes the high level summary and then collapses the other reporting data (impacted...

> "coverage decreases by -3%"...Perhaps it should say "coverage decreases: -3%" to make it more accurate? Thank you, @KnorpelSenf that makes sense - will update text clarification in next iteration.