Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

docs: update module registry URLs to correct path structure#18681

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
matifali merged 2 commits intomainfromupdate-registry-path
Aug 2, 2025

Conversation

f0ssel
Copy link
Contributor

@f0sself0ssel commentedJun 30, 2025
edited by coderabbitaibot
Loading

Summary

  • Updated documentation references to use the correct registry path structure
  • Changed URLs from incorrect paths to the correct format:
    • Modules main page: registry.coder.com/modules
    • Specific modules: registry.coder.com/modules/coder/{module-name}

Test plan

  • Verify that all documentation links to modules point to the correct URL structure

🤖 Generated withClaude Code

Summary by CodeRabbit

  • Documentation
    • Updated module URLs in the documentation to reflect the new path structure for registry links.

Updated all references to the Coder registry to use the correct path structure:- Modules page: registry.coder.com/modules- Module paths: registry.coder.com/modules/coder/{module-name}🤖 Generated with [Claude Code](https://claude.ai/code)Co-Authored-By: Claude <noreply@anthropic.com>
@f0sself0sselforce-pushed theupdate-registry-path branch froma682798 to8d5ef2dCompareJune 30, 2025 21:07
@f0sself0ssel changed the titledocs: update coder/modules references to coder/registry path structuredocs: update module registry URLs to correct path structureJun 30, 2025
@f0sselCoder
Copy link
ContributorAuthor

I've verified that there are no direct references to the GitHub repository 'coder/modules' that need updating. All direct Git URLs already use the correct path structure with 'registry/coder/modules/' format.

@github-actionsgithub-actionsbot added the staleThis issue is like stale bread. labelJul 8, 2025
@EdwardAngertEdwardAngert added docsArea: coder.com/docs and removed staleThis issue is like stale bread. labelsJul 8, 2025
@EdwardAngert
Copy link
Contributor

@f0ssel this looks ready to go as-is, but there are a few more that show up in search (VS Code andGitHub are giving me different results, but I haven't dug into why)

if you can mark thisReady for review I can approve and merge or investigate+change the others (and approve and merge)

@github-actionsgithub-actionsbot added the staleThis issue is like stale bread. labelJul 16, 2025
@EdwardAngert
Copy link
Contributor

bump

@EdwardAngertEdwardAngert removed the staleThis issue is like stale bread. labelJul 17, 2025
@github-actionsgithub-actionsbot added the staleThis issue is like stale bread. labelAug 1, 2025
@coderabbitaicoderabbitai
Copy link

coderabbitaibot commentedAug 1, 2025
edited
Loading

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

📥 Commits

Reviewing files that changed from the base of the PR and between6c4db7a and9f6c206.

📒 Files selected for processing (1)
  • docs/admin/templates/extending-templates/modules.md (1 hunks)
 ______________________________________________________< Nothing is more permanent than a temporary solution. > ------------------------------------------------------  \   \   (\__/)       (•ㅅ•)       /   づ

Tip

You can generate walkthrough in a markdown collapsible section to save space.

Enable thereviews.collapse_walkthrough setting in your project's settings in CodeRabbit to generate walkthrough in a markdown collapsible section.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branchupdate-registry-path

🪧 Tips

Chat

There are 3 ways to chat withCodeRabbit:

  • 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 oursupport 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 docstrings togenerate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for 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 theconfiguration 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 ourDocumentation for detailed information on how to use CodeRabbit.
  • Join ourDiscord Community to get help, request features, and share feedback.
  • Follow us onX/Twitter for updates and announcements.

@matifalimatifali removed the staleThis issue is like stale bread. labelAug 2, 2025
@matifalimatifali marked this pull request as ready for reviewAugust 2, 2025 01:02
@matifalimatifali merged commit6ba4b5b intomainAug 2, 2025
33 of 34 checks passed
@matifalimatifali deleted the update-registry-path branchAugust 2, 2025 01:03
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsAug 2, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@matifalimatifalimatifali approved these changes

Assignees

@f0sself0ssel

Labels

docsArea: coder.com/docs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@f0ssel@EdwardAngert@matifali

[8]ページ先頭

©2009-2025 Movatter.jp