-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
fix: add "cursor: pointer" to MemberBadge component #4075
Conversation
onearmy-community-platform Run #6758
Run Properties:
|
Project |
onearmy-community-platform
|
Branch Review |
pull/4075
|
Run status |
Passed #6758
|
Run duration | 05m 30s |
Commit |
192e98b683: fix: set profile button cursor style to pointer
|
Committer | CrowsVeldt |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
2
|
Pending |
0
|
Skipped |
0
|
Passing |
78
|
View all changes introduced in this branch ↗︎ |
I just realized that the MemberBadge is also used on the profile page where it's not a button. This change naively assumes the MemberBadge will always be a button. I'm working on correcting that now. |
Thanks for the first time contribution @CrowsVeldt! |
@all-contributors add @CrowsVeldt for code |
@CrowsVeldt already contributed before to code |
Oh wait, you also contributed a while back @CrowsVeldt. Thanks! |
🎉 This PR is included in version 2.27.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
PR Checklist
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The cursor is unchanged when hovering over the MemberBadge component
What is the new behavior?
The cursor changes to pointer when hovering over the MemberBadge component
Describe the new behaviour
If useful, provide screenshot or capture to highlight main changes
Does this PR introduce a breaking change?
Git Issues
Closes #
What happens next?
Thanks for the contribution! We try to make sure all PRs are reviewed ahead of our monthly maintainers call (first Monday of the month)
If the PR is working as intended it'll be merged and included in the next platform release, if not changes will be requested and re-reviewed once updated.
If you need more immediate feedback you can try reaching out on Discord in the Community Platform
development
channel.