Fix typo in URL

[mangelajo]

Summary by CodeRabbit

• Documentation
  • Updated installation instructions to use the new repository URL for the Jumpstarter installer script.

[coderabbitai]

Walkthrough

The documentation was updated to change the URLs for the Jumpstarter installer script, reflecting a new GitHub repository owner. All curl commands in the installation instructions now reference jumpstarter-dev/jumpstarter instead of the previous jumpstarter/jumpstarter. No other documentation or code changes were made.

Changes

File(s)	Change Summary
docs/source/getting-started/installation/packages.md	Updated installer script URLs to use the new jumpstarter-dev repository owner

Possibly related PRs

• Dependabot devcontainers ecosystem entry points to non-existent directory jumpstarter#562: Introduced and expanded the installer script and its documentation, which is directly referenced in the updated URLs.

Suggested reviewers

• kirkbrauer

Poem

A hop and a skip, the URLs shift,
To jumpstarter-dev, we make the lift.
Install commands now point anew,
So scripts will fetch the latest brew.
With every doc, we leap ahead—
Rabbits keep the links well-fed! 🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ec9b9b7 and 3699081.

📒 Files selected for processing (1)

• docs/source/getting-started/installation/packages.md (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#303
File: docs/source/_static/js/versions.js:27-27
Timestamp: 2025-02-20T17:46:31.609Z
Learning: In the Jumpstarter documentation system, version strings are sourced from Git tags during the build process and are controlled by maintainers, therefore HTML sanitization is not required when displaying these versions in the version selector.

Learnt from: NickCao
PR: jumpstarter-dev/jumpstarter#425
File: packages/jumpstarter-driver-tasmota/README.md:23-23
Timestamp: 2025-05-07T18:33:56.914Z
Learning: In Jumpstarter documentation, configuration parameters should be presented in markdown tables rather than bulleted lists for better readability.

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#483
File: docs/multiversion.sh:4-5
Timestamp: 2025-05-13T18:08:55.390Z
Learning: The multiversion.sh script in the docs directory is intentionally repository-specific with hardcoded branch names (including "main") and doesn't need to handle varying default branch names. Adding complexity for generalization isn't necessary.

docs/source/getting-started/installation/packages.md (6)

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#303
File: docs/source/_static/js/versions.js:27-27
Timestamp: 2025-02-20T17:46:31.609Z
Learning: In the Jumpstarter documentation system, version strings are sourced from Git tags during the build process and are controlled by maintainers, therefore HTML sanitization is not required when displaying these versions in the version selector.

Learnt from: NickCao
PR: jumpstarter-dev/jumpstarter#425
File: packages/jumpstarter-driver-tasmota/README.md:23-23
Timestamp: 2025-05-07T18:33:56.914Z
Learning: In Jumpstarter documentation, configuration parameters should be presented in markdown tables rather than bulleted lists for better readability.

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#483
File: docs/multiversion.sh:4-5
Timestamp: 2025-05-13T18:08:55.390Z
Learning: The multiversion.sh script in the docs directory is intentionally repository-specific with hardcoded branch names (including "main") and doesn't need to handle varying default branch names. Adding complexity for generalization isn't necessary.

Learnt from: NickCao
PR: jumpstarter-dev/jumpstarter#463
File: packages/jumpstarter-cli-admin/jumpstarter_cli_admin/get_test.py:270-270
Timestamp: 2025-05-28T15:09:35.768Z
Learning: The jumpstarter CLI is designed to match kubectl's behavior, including returning exit code 0 (success) when no resources are found, rather than exit code 1 (failure).

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#339
File: packages/jumpstarter-driver-flashers/oci_bundles/build_bundle.sh:12-12
Timestamp: 2025-03-12T16:55:13.031Z
Learning: For shell scripts in the Jumpstarter project, prefer using `set -e` at the beginning of scripts to handle errors consistently throughout, rather than adding explicit error checks like `|| exit 1` for individual commands.

Learnt from: mangelajo
PR: jumpstarter-dev/jumpstarter#239
File: .github/workflows/e2e.yaml:19-22
Timestamp: 2025-01-29T07:01:55.387Z
Learning: For GitHub Actions within the jumpstarter-dev organization (internal actions), using @main is acceptable as they are under the organization's control. SHA pinning is not required in this case.

🔇 Additional comments (2)

docs/source/getting-started/installation/packages.md (2)

27-27: Installer URL updated correctly
The new owner path jumpstarter-dev/jumpstarter resolves the original typo.

---

32-32: No lingering references to the old GitHub org detected

I ran a repository-wide search for raw.githubusercontent.com/jumpstarter/jumpstarter and found no occurrences. The installer URL has been updated consistently.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 docstrings to generate docstrings for this 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.

[netlify]

✅ Deploy Preview for jumpstarter-docs ready!

Name	Link
🔨 Latest commit	3699081
🔍 Latest deploy log	https://app.netlify.com/projects/jumpstarter-docs/deploys/6876498c7d2fb300089d4982
😎 Deploy Preview	https://deploy-preview-568--jumpstarter-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.