docs: update engine example links for grouped framework folders#69
Merged
Conversation
Contributor
|
Warning Review limit reached
Next review available in: 41 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (8)
WalkthroughThis PR updates GitHub reference links throughout the documentation across English, Chinese, Japanese, and Korean locales. Card and inline hyperlinks are repointed from older top-level example repository paths (e.g., anchor-counter, rust-counter, magic-actions, private-counter, gachapon, roll-dice) to newer nested subdirectory paths (e.g., counter/anchor, counter/native-rust, magic-actions/anchor, private-counter/anchor, gachapon-example, roll-dice/anchor). No content, structure, or code logic changes were made; only href/URL values were modified. ChangesExample repository link updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jonasXchen
approved these changes
Jul 3, 2026
jonasXchen
left a comment
jonasXchen
left a comment
Collaborator
There was a problem hiding this comment.
lgtm! we need to make sure the example and skills are synced
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@cn/pages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdx`:
- Around line 31-39: The test-folder GitHub link in the Rust guide is pointing
to a directory using blob instead of tree. Update the href values in the Card
entries for the native Rust tests link and the Pinocchio tests link so they use
tree/main/... paths rather than blob/main/... paths, keeping the surrounding
Card markup unchanged.
In `@cn/pages/get-started/how-integrate-your-program/rust.mdx`:
- Around line 52-58: The GitHub links for the TypeScript test scripts point to a
directory, but the current hrefs use the blob view, which won’t open folders
correctly. Update the three tests link targets in the relevant MDX sections for
the Rust guide to use the tree view instead, and verify the Card entries labeled
for the tests still point to the same repository path via the correct directory
URL format.
In `@ko/pages/get-started/how-integrate-your-program/rust.mdx`:
- Around line 52-58: The GitHub links for the tests folder are using blob-style
URLs even though they point to a directory, so they will not open correctly;
update the relevant card/link entries in the Rust docs (including the ones
referenced by the tests folder links) to use tree-style URLs instead. Use the
existing link targets in the Rust page sections with the TypeScript/Rust
examples as the anchor points, and make sure every folder link to tests
consistently uses tree so the directory renders properly on GitHub.
In `@pages/ephemeral-rollups-ers/how-to-guide/quickstart.mdx`:
- Line 238: The card links in quickstart.mdx are pointing at the wrong example
path segment; update the href targets in the quickstart cards so they go to the
correct example directories under /magic-actions and /delegation-actions. Use
the existing card/link entries in the quickstart content to locate the affected
href values and replace the /anchor suffix with the intended directory names.
In `@pages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdx`:
- Around line 31-39: The Rust tests links in the how-to guide currently point to
paths that will 404 on the example repo’s main branch, so gate these hrefs
behind the `magicblock-engine-examples#108` refactor or update them to match the
current `rust-counter` and `pinocchio-counter` paths. Make the same
conditional/link fix in the related Card entries in this guide and in the
localized copies, using the existing link-rendering markup around the Rust tests
section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: a704b14e-eee3-4c7a-ab93-775118f902f5
📒 Files selected for processing (90)
cn/pages/ephemeral-rollups-ers/how-to-guide/quickstart.mdxcn/pages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdxcn/pages/ephemeral-rollups-ers/introduction/ephemeral-accounts.mdxcn/pages/ephemeral-rollups-ers/introduction/magic-router.mdxcn/pages/ephemeral-rollups-ers/magic-actions/client.mdxcn/pages/ephemeral-rollups-ers/magic-actions/implementation.mdxcn/pages/ephemeral-rollups-ers/magic-actions/overview.mdxcn/pages/ephemeral-rollups-ers/magic-actions/troubleshooting.mdxcn/pages/get-started/how-integrate-your-program/anchor.mdxcn/pages/get-started/how-integrate-your-program/rust.mdxcn/pages/get-started/use-cases/payments.mdxcn/pages/private-ephemeral-rollups-pers/how-to-guide/access-control.mdxcn/pages/templates/counter.mdxcn/pages/templates/gachapon.mdxcn/pages/templates/onchain-dice.mdxcn/pages/templates/rock-paper-scissors.mdxcn/pages/tools/crank/introduction.mdxcn/snippets/oncurve-delegation.mdxcn/snippets/quick-access-er-rust.mdxcn/snippets/quick-access-er.mdxcn/snippets/quick-access-per.mdxcn/snippets/quick-access-vrf.mdxjp/pages/ephemeral-rollups-ers/how-to-guide/quickstart.mdxjp/pages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdxjp/pages/ephemeral-rollups-ers/introduction/ephemeral-accounts.mdxjp/pages/ephemeral-rollups-ers/introduction/magic-router.mdxjp/pages/ephemeral-rollups-ers/magic-actions/client.mdxjp/pages/ephemeral-rollups-ers/magic-actions/implementation.mdxjp/pages/ephemeral-rollups-ers/magic-actions/overview.mdxjp/pages/ephemeral-rollups-ers/magic-actions/troubleshooting.mdxjp/pages/get-started/how-integrate-your-program/anchor.mdxjp/pages/get-started/how-integrate-your-program/rust.mdxjp/pages/get-started/use-cases/payments.mdxjp/pages/private-ephemeral-rollups-pers/how-to-guide/access-control.mdxjp/pages/templates/counter.mdxjp/pages/templates/gachapon.mdxjp/pages/templates/onchain-dice.mdxjp/pages/templates/rock-paper-scissors.mdxjp/pages/tools/crank/introduction.mdxjp/snippets/oncurve-delegation.mdxjp/snippets/quick-access-er-rust.mdxjp/snippets/quick-access-er.mdxjp/snippets/quick-access-per.mdxjp/snippets/quick-access-vrf.mdxko/pages/ephemeral-rollups-ers/how-to-guide/quickstart.mdxko/pages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdxko/pages/ephemeral-rollups-ers/introduction/ephemeral-accounts.mdxko/pages/ephemeral-rollups-ers/introduction/magic-router.mdxko/pages/ephemeral-rollups-ers/magic-actions/client.mdxko/pages/ephemeral-rollups-ers/magic-actions/implementation.mdxko/pages/ephemeral-rollups-ers/magic-actions/overview.mdxko/pages/ephemeral-rollups-ers/magic-actions/troubleshooting.mdxko/pages/get-started/how-integrate-your-program/anchor.mdxko/pages/get-started/how-integrate-your-program/rust.mdxko/pages/get-started/use-cases/payments.mdxko/pages/private-ephemeral-rollups-pers/how-to-guide/access-control.mdxko/pages/templates/counter.mdxko/pages/templates/gachapon.mdxko/pages/templates/onchain-dice.mdxko/pages/templates/rock-paper-scissors.mdxko/pages/tools/crank/introduction.mdxko/snippets/oncurve-delegation.mdxko/snippets/quick-access-er-rust.mdxko/snippets/quick-access-er.mdxko/snippets/quick-access-per.mdxko/snippets/quick-access-vrf.mdxpages/ephemeral-rollups-ers/how-to-guide/quickstart.mdxpages/ephemeral-rollups-ers/how-to-guide/rust-program.mdxpages/ephemeral-rollups-ers/how-to-guide/rust-tests.mdxpages/ephemeral-rollups-ers/introduction/ephemeral-accounts.mdxpages/ephemeral-rollups-ers/introduction/magic-router.mdxpages/ephemeral-rollups-ers/magic-actions/client.mdxpages/ephemeral-rollups-ers/magic-actions/implementation.mdxpages/ephemeral-rollups-ers/magic-actions/overview.mdxpages/ephemeral-rollups-ers/magic-actions/troubleshooting.mdxpages/get-started/how-integrate-your-program/anchor.mdxpages/get-started/how-integrate-your-program/rust.mdxpages/get-started/use-cases/payments.mdxpages/private-ephemeral-rollups-pers/how-to-guide/access-control.mdxpages/private-ephemeral-rollups-pers/how-to-guide/quickstart.mdxpages/templates/counter.mdxpages/templates/gachapon.mdxpages/templates/onchain-dice.mdxpages/templates/rock-paper-scissors.mdxpages/tools/crank/introduction.mdxsnippets/oncurve-delegation.mdxsnippets/quick-access-er-rust.mdxsnippets/quick-access-er.mdxsnippets/quick-access-per.mdxsnippets/quick-access-vrf.mdx
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Merge order
Depends on magicblock-labs/magicblock-engine-examples#108.
Do not merge this PR until magicblock-labs/magicblock-engine-examples#108 is merged, otherwise these links will point to paths that do not exist on
main.Summary
Updates docs links to
magicblock-engine-examplesafter the example repo refactor that groups implementations by use case and framework.Changes
anchor-counter->counter/anchorrust-counter->counter/native-rustpinocchio-counter->counter/pinocchiomagic-actions->magic-actions/anchorroll-dice->roll-dice/anchorValidation
git diff --checknpx -y mintlify validateBreaking changes
None for the docs site after magicblock-labs/magicblock-engine-examples#108 is merged. Before that dependency merges, the updated external links target paths that are not yet on the examples repo
mainbranch.Summary by CodeRabbit