Gitpod setup And Bio Detail Overflow Bug Fixed
What does this PR do?
#8823 Add Gitpod integration to the repo for faster setup I have included a Gitpod button that enables users to quickly set up a repository. Additionally, I have added an automatic provisioning command in the .gitpod.yml file to facilitate this process. To provide clarity on these updates, I have also made changes to the readme file.
#8822 Also, Added word-wrap property to the div containing biodetails.
http://www.giphy.com/gifs/2K3HQygajMdnMBsMSw
Fixes # (issue)
Add Gitpod integration to the repo for faster setup https://github.com/calcom/cal.com/issues/8823#issue-1704065692
Bio details overflow issue on user profile https://github.com/calcom/cal.com/issues/8822#issue-1704045262
##Bio details Before PR
##Bio details After PR
Loom Video :
https://www.loom.com/share/901be1b5de114601bae5ecab207dfc4e
Environment: Staging(main branch) / Production
Type of change
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- This change requires a documentation update
How should this be tested?
- [x] Bio details no longer overflowing.
- [x] Gitpod working correctly.
Adding Gitpod to the repo would provide the following benefits:
- Faster development setup time
- Increased flexibility for developers to work from any device or location
- Reduced frustration for developers who struggle with setting up development environments
- Easier collaboration and code review process
@Chiranjeev-droid is attempting to deploy a commit to the cal Team on Vercel.
A member of the Team first needs to authorize it.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| cal | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 13, 2023 5:05pm |
| ui | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | May 13, 2023 5:05pm |
📦 Next.js Bundle Analysis for @calcom/web
This analysis was generated by the Next.js Bundle Analysis action. 🤖
Eight Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/apps/[slug]/[...pages] |
456.8 KB |
607.69 KB | 173.63% (🟡 +0.16%) |
/auth/setup |
174.8 KB |
325.69 KB | 93.06% (🟡 +0.15%) |
/event-types |
416.62 KB |
567.52 KB | 162.15% (🟢 -2.63%) |
/event-types/[type] |
468.73 KB |
619.63 KB | 177.04% (🟢 -2.44%) |
/getting-started/[[...step]] |
416.44 KB |
567.33 KB | 162.09% (🟢 -2.62%) |
/settings/my-account/profile |
362.12 KB |
513.02 KB | 146.58% (🟢 -2.63%) |
/settings/teams/[id]/profile |
357.5 KB |
508.39 KB | 145.26% (🟢 -2.63%) |
/workflows/[workflow] |
358.05 KB |
508.94 KB | 145.41% (🟢 -2.62%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/-
Prebuilds reduce wait time, by installing dependencies or running builds before starting a new workspace.
The github section defines various settings related to GitHub, such as enabling prebuilds for the master branch and pull requests, adding checks and comments, and adding a badge.
The vscode section specifies a list of extensions for Visual Studio Code that should be installed for this project. These include extensions for linting and formatting Markdown, linting and formatting code using Prettier and ESLint, working with Tailwind CSS, and using Stripe and Prisma
@zomars how do you feel about gitpod? should we merge this?