-
Notifications
You must be signed in to change notification settings - Fork 235
feat: add badge component #2305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Tachometer resultsCurrently, no packages are changed by this PR... |
b0e7469 to
3346ff5
Compare
Westbrook
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super excited to see this FINALLY landing!
ac5d05a to
f080086
Compare
najikahalsema
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Nice work, Hunter!
f080086 to
62236c8
Compare
fba4a02 to
ec224b5
Compare
Westbrook
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! 💯 Thanks for the slog with the various teams to bring this over the line. 🙇🏼♂️ With this I dare say that you onboarding is finally complete 😜
Description
Implements the Badge component.
Related issue(s)
#1643
Motivation and context
Expanding component coverage
How has this been tested?
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main.