Skip to content

Same component for other teams page#12196

Closed
ibex088 wants to merge 12 commits intocalcom:mainfrom
ibex088:same-component-for-other-teams-page
Closed

Same component for other teams page#12196
ibex088 wants to merge 12 commits intocalcom:mainfrom
ibex088:same-component-for-other-teams-page

Conversation

@ibex088
Copy link
Copy Markdown
Contributor

@ibex088 ibex088 commented Nov 2, 2023

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented Nov 2, 2023

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

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Nov 2, 2023

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Same component for other teams page". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Nov 2, 2023

📦 Next.js Bundle Analysis for @calcom/web

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

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/settings/organizations/teams/other/[id]/members 375.57 KB 531.67 KB 151.91% (🔴 +33.68%)
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 "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@CarinaWolli CarinaWolli requested a review from a team November 2, 2023 18:10
@github-actions
Copy link
Copy Markdown
Contributor

Hey there, there is a merge conflict, can you take a look?

@github-actions github-actions Bot added the 🚨 merge conflict This PR has a merge conflict that has to be addressed label Nov 21, 2023
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Dec 6, 2023

This PR is being marked as stale due to inactivity.

@github-actions github-actions Bot added Stale and removed Stale labels Dec 6, 2023
@ibex088 ibex088 closed this Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🚨 merge conflict This PR has a merge conflict that has to be addressed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants