[ignore] Dummry issue to draft UTR message

[agraebe]

Context

We started the UTR workstream by recapping what we know about the customer needs. We documented the initial product decision in the same document.

Content Requirements

The key factors for the GitHub comment are:

• users only care about failed test runs
• success and skipped runs only need a count
• failed test runs should include a list of all test runs with the following details: test name, failure type, link to logs

Because we are building a flaky test solution, I suggest we also annotate failed test runs associated with flaky tests.

Draft proposal

48 tests were run on e7d148a. 22 failed. 2 skipped. 24 passed. View Full Report ↗︎

First 5 failed test runs:

Test name	Failure reason	Flaky	Logs
Check switches through onboarding flow for existing users who already have uploads	A test exceeded the timeout of 40000 ms, so you should increase the timeout value or optimize the test to run faster.		Logs
Check has different onboarding states for different repos	A test exceeded the timeout of 10000 ms, so you should increase the timeout value or optimize the test to run faster.		Logs
Check switches through onboarding flow for existing users who already have uploads	A test exceeded the timeout of 40000 ms, so you should increase the timeout value or optimize the test to run faster.	⚠️	Logs
Check switches through onboarding flow for existing users who already have uploads	A test exceeded the timeout of 40000 ms, so you should increase the timeout value or optimize the test to run faster.		Logs
Check has different onboarding states for different repos	A test exceeded the timeout of 10000 ms, so you should increase the timeout value or optimize the test to run faster.	⚠️	Logs

... and 17 more