-
Notifications
You must be signed in to change notification settings - Fork 2k
chore: standardize type check job name to check-types #9973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@Asupkay is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
anthonyshew
approved these changes
Feb 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thank you!
joshnuss
pushed a commit
to joshnuss/turborepo
that referenced
this pull request
Feb 15, 2025
### Description This pull request standardizes the type checking task name to `check-types` across all example repos. This is good so that new users can learn one way and feel confident they will be able to run this across all repos that need it. ### Testing Instructions Running `turbo check-types` in `with-shell-commands` example  Running `pnpm check-types` in `with-typeorm` repo  Running `pnpm check-types` in `with-gatsby/apps/web`  Running `pnpm check-types` and `pnpm build` in `with-vue-next/apps/web`  --------- Co-authored-by: Anthony Shew <anthony.shew@vercel.com>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: examples
Improvements or additions to examples
needs: triage
New issues get this label. Remove it after triage
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request standardizes the type checking task name to
check-types
across all example repos. This is good so that new users can learn one way and feel confident they will be able to run this across all repos that need it.Testing Instructions
Running
turbo check-types
inwith-shell-commands
exampleRunning
pnpm check-types
inwith-typeorm
repoRunning

pnpm check-types
inwith-gatsby/apps/web
Running

pnpm check-types
andpnpm build
inwith-vue-next/apps/web