cal.com chore: move calcom/docs into mono repo

trafficstars

What does this PR do?

Fixes #14772

Requirement/Documentation

If there is a requirement document, please, share it here.
If there is a UI/UX design document, please, share it here.

Type of change

Bug fix (non-breaking change which fixes an issue)
Chore (refactoring code, technical debt, workflow improvements)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Tests (Unit/Integration/E2E or any other test)
This change requires a documentation update

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

Mandatory Tasks

[ ] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

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 PR needs changes to the documentation
I haven't checked if my changes generate no new warnings
I haven't added tests that prove my fix is effective or that my feature works
I haven't checked if new and existing unit tests pass locally with my changes

May 06 '24 22:05 anikdhabal

@anikdhabal is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

May 06 '24 22:05 vercel[bot]

Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link.

May 06 '24 22:05 github-actions[bot]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem, network, shell, unsafe Transitive: eval	`+301`	188 MB	vercel-release-bot
npm/[email protected]	network Transitive: environment, eval, filesystem, shell, unsafe	`+500`	47.1 MB	quietshu
npm/[email protected]	environment, shell Transitive: eval, filesystem, network	`+219`	6.64 MB	quietshu
npm/[email protected]	environment, filesystem, unsafe	`0`	11.2 MB	prettier-bot
npm/[email protected]	environment	`+1`	3.1 MB	gaearon

View full report↗︎

May 06 '24 22:05 socket-security[bot]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: install Source: `node install.js`	`apps/docs/legacy/package.json`
Telemetry	npm/[email protected]	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	`apps/docs/legacy/package.json`
Install scripts	npm/@ampproject/[email protected]	Install script: postinstall Source: `node lib/warmup.js`	`apps/docs/legacy/package.json`
Telemetry	npm/[email protected]	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	`apps/docs/legacy/package.json`
Protestware/Troll package	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	`apps/docs/legacy/package.json`
Install scripts	npm/[email protected]	Install script: postinstall Source: `node -e "try{require('./_postinstall')}catch(e){}" \|\| exit 0`	`apps/docs/legacy/package.json`

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package my come along with functionality unrelated to its primary purpose.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@ampproject/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]

May 06 '24 22:05 socket-security[bot]

Graphite Automations

"Add community label" took an action on this PR • (05/06/24)

1 label was added to this PR based on Keith Williams's automation.

"Add foundation team as reviewer" took an action on this PR • (05/06/24)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add consumer team as reviewer" took an action on this PR • (05/06/24)

1 reviewer was added to this PR based on Keith Williams's automation.

May 06 '24 22:05 graphite-app[bot]

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

Seven 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`)
`/event-types`	`556.73 KB`	785.3 KB	224.37% (🟡 +0.18%)
`/getting-started/[[...step]]`	`405.19 KB`	633.76 KB	181.08% (🟡 +0.18%)
`/settings/my-account/profile`	`406.02 KB`	634.6 KB	181.31% (🟡 +0.19%)
`/settings/organizations/profile`	`398.79 KB`	627.37 KB	179.25% (🟡 +0.18%)
`/settings/organizations/teams/other/[id]/profile`	`469.2 KB`	697.77 KB	199.36% (🟡 +0.19%)
`/settings/teams/[id]/profile`	`470.03 KB`	698.6 KB	199.60% (🟡 +0.18%)
`/workflows/[workflow]`	`410.63 KB`	639.21 KB	182.63% (🟡 +0.18%)

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 "+/-

May 06 '24 23:05 github-actions[bot]

Thanks for this @anikdhabal but unfortunately we weren't able to get it merged quickly enough and now there have been structural changes to docs. We'll need to redo this PR. We can take it internally to make sure it's done in 1 motion and nothing is lost in the move.

May 23 '24 13:05 keithwillcode

Thanks for this @anikdhabal but unfortunately we weren't able to get it merged quickly enough and now there have been structural changes to docs. We'll need to redo this PR. We can take it internally to make sure it's done in 1 motion and nothing is lost in the move.

Sure Keith, understandable.

May 23 '24 13:05 anikdhabal

cal.com cal.com copied to clipboard

chore: move calcom/docs into mono repo

What does this PR do?

Requirement/Documentation

Type of change

How should this be tested?

Mandatory Tasks

Checklist

Next steps

Graphite Automations

📦 Next.js Bundle Analysis for @calcom/web

Seven Pages Changed Size

cal.com
cal.com copied to clipboard