Skip to content

docs(repo): Update typedoc guides #6353

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

NWylynko
Copy link
Contributor

@NWylynko NWylynko commented Jul 18, 2025

Description

I've moved the generated files to be directly in the clerk-docs repo. Updating the documentation in this repo to reflect that.

Alongside these prs to update the guides in those relevant places.
clerk/clerk-docs#2437
https://github.com/clerk/clerk/pull/1399

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Documentation
    • Updated documentation to reflect the correct repository and path where Typedoc-generated files are published.
    • Clarified instructions regarding the destination of generated documentation in CI workflows.
    • Improved accuracy of contribution guidelines related to accessing and publishing Typedoc files.

Copy link

changeset-bot bot commented Jul 18, 2025

⚠️ No Changeset found

Latest commit: 6b97468

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jul 18, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 18, 2025 10:44pm

Copy link
Contributor

coderabbitai bot commented Jul 18, 2025

📝 Walkthrough

Walkthrough

The changes update documentation files to correct the referenced destination repository for generated Typedoc documentation. The previous documentation stated that generated docs were pushed to the clerk/generated-typedoc repository. This has been updated to reflect that the docs are actually pushed to the clerk/clerk-docs repository under the clerk-typedoc directory. No changes were made to the workflows, code, or exported/public entities; only the documentation text was revised for accuracy regarding the location of generated documentation files.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/CONTRIBUTING.md (1)

183-186: Typo in folder name two lines above

Line 183 still references .typdoc/docs (missing the e). Fixing it prevents confusion for new contributors.

- Locally, you can run `pnpm run typedoc:generate` to generate the docs. Afterwards, you can inspect the MDX files inside `.typdoc/docs`.
+ Locally, you can run `pnpm run typedoc:generate` to generate the docs. Afterwards, you can inspect the MDX files inside `.typedoc/docs`.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 438e499 and 6b97468.

📒 Files selected for processing (3)
  • .typedoc/README.md (1 hunks)
  • docs/CICD.md (1 hunks)
  • docs/CONTRIBUTING.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
docs/**/*

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/monorepo.mdc
**/*

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

🧠 Learnings (1)
docs/CONTRIBUTING.md (1)
Learnt from: CR
PR: clerk/javascript#0
File: docs/CONTRIBUTING.md:0-0
Timestamp: 2025-07-18T15:23:03.087Z
Learning: If you find a typo in a Typedoc-generated file, edit the source file and open a PR to merge the fix to `main`.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: Build Packages
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
.typedoc/README.md (1)

74-75: Looks good – please double-check CI configuration

The repository path has been updated correctly. Ensure the GH Actions job that pushes ./.typedoc/docs has already been switched to clerk/clerk-docs/clerk-typedoc; otherwise CI will still open PRs against the old repository.

docs/CICD.md (1)

17-18: LGTM – destination repo updated

The workflow-dispatch target now points at clerk/clerk-docs, matching the other docs.

Copy link

pkg-pr-new bot commented Jul 18, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6353

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6353

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6353

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6353

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6353

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6353

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6353

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6353

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6353

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6353

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6353

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6353

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6353

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6353

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6353

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6353

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6353

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6353

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6353

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6353

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6353

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6353

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6353

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6353

commit: 6b97468

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants