style fix: update hovers styling on leave site button.#1737
Open
haseeb-iqbal wants to merge 4 commits intochaynHQ:developfrom
Open
style fix: update hovers styling on leave site button.#1737haseeb-iqbal wants to merge 4 commits intochaynHQ:developfrom
haseeb-iqbal wants to merge 4 commits intochaynHQ:developfrom
Conversation
|
@haseeb-iqbal is attempting to deploy a commit to the Chayn Team on Vercel. A member of the Team first needs to authorize it. |
bl00dymarie
approved these changes
Mar 16, 2026
Author
|
@bl00dymarie It looks like the Vercel build needs authorization to be deployed. After that I believe the PR can be merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Resolves #1735
What changes did you make and why did you make them?
Refactored styling
breadcrumbButtonStyleand split it into two componentsbreadcrumbButtonStyleandbreadcrumbPositionStyleto as suggested in the issue description.Did you run tests? Share screenshot of results:
leave.site.Issue.fixed2.webm
How did you find us? (GitHub, Google search, social media, etc.):
Github
PR CHECKLIST:
Before submitting, check that you have completed the following tasks: