Feature: YOLO Coders Component

[isabensusan]

Suggested solution

Context

We have introduced the YOLO Metric in the API to signal users that have been pushing commits directly to the main branch on a project. This component aims to surface this data in the front end, and signal to the user when there's a YOLO coder in a project.

Mockup (figma)

[github-actions[bot]]

Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.

To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please comment on this issue.

For full info on how to contribute, please check out our contributors guide.

[jpmcb]

👏🏼 👏🏼 👏🏼

This is amazing! Great design!

---

• "maintainer", "external", "member", etc. might be abit difficult to derive from the push data in the API that is surfaced in the yolo coders endpoint. I.e., that metadata doesn't go along with those pushes. We could probably look in the prs, pr reviews, or issue comments to determine that.
  • On that note, adding this data to the lottery factor wouldn't be too bad since that data goes alongside the pull requests in the "pr_author_association" column
• Should be able to construct the GitHub sha link as https://github.com/{org}/{name}/commit/{head_sha} and that'd take you right to the head commit push. It's tricky to try to show the full range of multiple commits that get pushed at once. But in theory, you should be able to see what was pushed from the last HEAD - we'll have to play around with this to validate

[jpmcb]

Supersede https://github.com/open-sauced/app/issues/3584 (although, still relevant context there on how the API endpoint works)