Audit: uploads

[codecovdesign]

Problem to solve

Audit the current UX and touchpoints of uploads: user expectations, how they are used, how uploads are visualized, and how users troubleshoot with them.

In Codecov, uploads refer to the process of sending coverage reports generated repo's your CI/CD pipeline or local testing environment to the Codecov platform. These reports are typically generated after running tests on codebase, specific to programming language used. Here is the general workflow of an upload:

1. Generate coverage report: after running tests, a coverage report is generated detailing which code was executed.
2. Upload to Codecov: this report is uploaded to Codecov, typically as part of your CI/CD pipeline.
3. Codecov analysis: codecov processes and analyzes the coverage data.
4. Insights: developers receive insights into code coverage, highlighting areas for potential improvement.

### Bugs
- [ ] https://github.com/codecov/codecov-cli/issues/351
- [ ] https://github.com/codecov/engineering-team/issues/1475

### Related issues
- [ ] https://github.com/codecov/engineering-team/issues/1086
- [ ] https://github.com/codecov/engineering-team/issues/201
- [ ] https://github.com/codecov/engineering-team/issues/1128
- [ ] https://github.com/codecov/engineering-team/issues/1534
- [ ] https://github.com/codecov/engineering-team/issues/1535
- [ ] https://github.com/codecov/engineering-team/issues/203
- [ ] https://github.com/codecov/engineering-team/issues/1536
- [ ] https://github.com/codecov/engineering-team/issues/264
- [ ] https://github.com/codecov/engineering-team/issues/1061
- [ ] Rename "Uploads" to "Coverage reports" in the UI and doc
- [ ] https://github.com/codecov/engineering-team/issues/2499
- [ ] https://github.com/codecov/engineering-team/issues/2498

### Backend improvements
- [ ] https://github.com/codecov/engineering-team/issues/1520

[Adal3n3]

Here is the design exploration for uploads. We will review it tomorrow to see which direction we should move forward. Figma: link

[Adal3n3]

@codecovdesign @aj-codecov @rohan-at-sentry @katia-sentry

Here are the prioritized upload issues for your review. Please add your comments here if you have thoughts on the ordering. Happy to move around the ordering of the issues if you think one is more important than others.

To view the combined designs view, go here

To view the individual design changes that's based on the issue, you can use the issues here or navigate to the pages on Figma.

[Adal3n3]

Just want to glue some documents here:

1. How a commit gets from upload to report to notification
2. This is the real Processing upload

[codecovdesign]

@spalmurray-codecov for sprint 150 could you review this with @Adal3n3, then we can groom some of the iterations for future sprints? cc @katia-sentry

[Adal3n3]

@codecovdesign @katia-sentry, @spalmurray-codecov and I had synced 2 weeks ago and I didn't post a note here. I should have posted a note for our sync.

issue	Eng work (day)	Note
https://github.com/codecov/engineering-team/issues/201	1	-
https://github.com/codecov/engineering-team/issues/1128	2-3	Pagination with filter takes a sprint so we are going for without pagination filter and including search by flag name, etc
https://github.com/codecov/engineering-team/issues/1535	1-2	Need design tweak
https://github.com/codecov/engineering-team/issues/203	1	-
https://github.com/codecov/engineering-team/issues/1536	10 days	Bulk download might take around a sprint and require API work. No need platform work
https://github.com/codecov/engineering-team/issues/2499	deprioritize	we didn't review this issue

Beside 1536 and 2499 we can wrap this issue in a sprint.