feat: Remove rate workflow from free workflow templates and ask to upgrade to teams plan or above.

[Jynx2004]

What does this PR do?

• Fixes [CAL-5121] Remove rate workflow from free workflow templates and ask to upgrade to teams plan or above. #19063 (GitHub issue number)

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

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

[CLAassistant]

All committers have signed the CLA.

[vercel]

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

A member of the Team first needs to authorize it.

[github-actions]

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 "[CAL-5121] Remove rate workflow from free workflow templates and ask to upgrade to teams plan or above. #19063". 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

[graphite-app]

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (02/03/25)

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

"Add community label" took an action on this PR • (02/03/25)

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

[retrogtx]

Hi @Jynx2004, thank you for your PR!
Can you please update the relevant sections in the PR description?

The checklist and more..

[retrogtx]

Could you please tell me how is this related to the original issue?

<h4 className="text-emphasis mb-4 font-medium">{t("cannot_book_this_far_in_the_future")}</h4> {/* <Button onClick={nextMonthButton} color="primary" EndIcon="arrow-right" data-testid="view_next_month">

[retrogtx]

I suppose you added previous commits too, will get those in check with the current issue that's in focus

[retrogtx]

please approve the description with relevant information

[CarinaWolli]

We might add ratings to the API, so we maybe want to keep it for free users. Requesting changes for nor until a decision is made. Thank you for your contribution 🙏

[Jynx2004]

We might add ratings to the API, so we maybe want to keep it for free users. Requesting changes for nor until a decision is made. Thank you for your contribution 🙏

Well that should be a good solution . Because right now i have provided the solution in frontend .

[Jynx2004]

please approve the description with relevant information

Next Time , i will make sure .

[Jynx2004]

Could you please tell me how is this related to the original issue?

<h4 className="text-emphasis mb-4 font-medium">{t("cannot_book_this_far_in_the_future")}</h4> {/* <Button onClick={nextMonthButton} color="primary" EndIcon="arrow-right" data-testid="view_next_month">

I think this issue has been closed before , so i will undo the changes

[Jynx2004]

Hi @Jynx2004, thank you for your PR! Can you please update the relevant sections in the PR description?

The checklist and more..

Yes Sure

[Jynx2004]

I suppose you added previous commits too, will get those in check with the current issue that's in focus

Sure