cal.com
cal.com copied to clipboard
fix: top right section overflow for event page
Fixes #14682
Prev:
After Changes:
Mandatory Tasks (DO NOT REMOVE)
- [X] I have self-reviewed the code (A decent size PR without self-review might be rejected)
- [ ] I have added a Docs issue here if this PR makes changes that would require a documentation change
- [ ] I have added or modified automated tests that prove my fix is effective or that my feature works (PRs might be rejected if logical changes are not properly tested)
How should this be tested?
- Are there environment variables that should be set?
- What are the minimal test data to have?
- What is expected (happy path) to have (input and output)?
- Any other important info that could help to test that PR
Checklist
- I haven't read the contributing guide
- My code doesn't follow the style guidelines of this project
- I haven't commented my code, particularly in hard-to-understand areas
- I haven't checked if my changes generate no new warnings
@Afrin127329 is attempting to deploy a commit to the cal Team on Vercel.
A member of the Team first needs to authorize it.
Thank you for following the naming conventions! ๐ Feel free to join our discord and post your PR link.
Graphite Automations
"Add community label" took an action on this PR โข (05/18/24)
1 label was added to this PR based on Keith Williams's automation.
"Add consumer team as reviewer" took an action on this PR โข (05/18/24)
1 reviewer was added to this PR based on Keith Williams's automation.
๐ฆ Next.js Bundle Analysis for @calcom/web
This analysis was generated by the Next.js Bundle Analysis action. ๐ค
This PR introduced no changes to the JavaScript bundle! ๐