op-deployer: Remove source build instructions

[mslipper]

These were causing confusion, since the source build instructions were much bigger than the (recommended) binary build instructions.

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	8744919
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/6745edf91afb810008abad20
😎 Deploy Preview	https://deploy-preview-1143--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

Walkthrough

The changes in this pull request involve modifications to the documentation for the op-deployer tool, specifically within the pages/builders/chain-operators/tools/op-deployer.mdx file. The primary alteration is the removal of the section that outlined the installation process from source, which included instructions for cloning the monorepo and building the binary. This section has been entirely deleted, resulting in a streamlined installation guide that now emphasizes downloading the latest release from the monorepo's release page.

The overall structure of the documentation remains unchanged, with sections dedicated to deployment usage and bootstrap usage still intact. The content related to the operational commands for op-deployer, including initialization, application, and inspection of deployments, has not been modified. The changes focus solely on refining the documentation by eliminating less common installation methods, thereby simplifying the guidance for users.

Possibly related PRs

• op-deployer + opcm documentation #934: This PR introduces documentation for the op-deployer tool, which is directly related to the changes made in the main PR that modifies the documentation for the same tool.
• Op deployer updates #1020: This PR updates the op-deployer documentation, aligning with the main PR's focus on refining the installation instructions and overall clarity of the op-deployer tool documentation.
• fix op-deployer commands #1121: This PR fixes command syntax in the op-deployer documentation, which is relevant to the main PR's changes that also aim to improve the clarity and usability of the op-deployer tool.
• adding op-deployer callouts #1016: This PR adds callouts in the documentation to direct users to the op-deployer tool, which complements the main PR's updates to the same documentation.
• Documentation Improvements: Grammar, Structure, and Readability Fixes #1057: This PR focuses on grammar and readability improvements across the documentation, which may include the op-deployer documentation that is also refined in the main PR.

Suggested reviewers

• bradleycamacho

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 555806a and 8744919.

📒 Files selected for processing (1)

• pages/builders/chain-operators/tools/op-deployer.mdx (0 hunks)

💤 Files with no reviewable changes (1)

• pages/builders/chain-operators/tools/op-deployer.mdx

---

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.