tutorials: make geth before using geth init

[jsvisa]

Description

We need to build the op-geth binary, else the following build/bin/geth init failed with No such file or directory

Tests

Additional context

Metadata

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	80c5b18
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67208b2cf05ae90008a47b9a
😎 Deploy Preview	https://deploy-preview-1042--docs-optimism.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 site configuration.

[coderabbitai]

Walkthrough

The changes in this pull request enhance the tutorial for creating an L2 rollup testnet by adding a new section on building the op-geth binary and incorporating various callouts to provide warnings and important notes. The sequence of operations is modified to include the new build instructions before initializing op-geth. Additionally, minor formatting adjustments and clarifications have been made throughout the document to improve user understanding of the setup process.

Changes

File Path	Change Summary
pages/builders/chain-operators/tutorials/create-l2-rollup.mdx	Added a section for building the op-geth binary and included various callouts for warnings and important notes. Minor formatting adjustments were also made.

Possibly related issues

• [2024 Q4 Audit] builders/chain-operators/tutorials/create-l2-rollup.mdx #917: The tutorial update aligns with the need for revisions due to the underlying tooling changes and the introduction of op-deployer.

Possibly related PRs

• Fix artifacts in 'Create L2 Rollup' tutorial #741: Modifies the same tutorial file by removing a code snippet and updating a command, relevant to the current changes.
• Update create-l2-rollup.mdx #824: Introduces updates to command-line options and documentation in the same tutorial file, aligning with the current enhancements.
• fix: wrong Deploy.s.sol file path #1019: Corrects the file path for the Deploy.sol script in the same tutorial, directly related to the changes involving the op-geth binary.

Suggested labels

tutorial

Suggested reviewers

• sbvegan

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between ea5c9ce and 80c5b18.

📒 Files selected for processing (1)

• pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

• Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
• Avoid gender-specific language and use the imperative form.
• Monitor capitalization for emphasis. Avoid using all caps, italics, or bold for emphasis.
• Ensure proper nouns are capitalized in sentences.
• Apply the Oxford comma.
• Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
• Use correct spelling and grammar at all times (IMPORTANT).
• Use sentence case for H1, H2, and H3 headers, capitalizing only the first word and any proper nouns.
• For all headers (H1, H2, H3), do not change the capitalization of proper nouns; keep them as they are.
  "