Skip to content

Conversation

@tamir-cow
Copy link
Contributor

@tamir-cow tamir-cow commented Nov 26, 2025

Updated sidebar positions and added notes regarding the bonding pool.
Important: Removed from_shadow_to_prod.md from sidebar as I merged its contents with onboarding doc.

Summary by CodeRabbit

  • Documentation
    • Marked "From Shadow to Prod" solver guide as draft.
    • Adjusted tutorial navigation order (onboarding, local test, routes integration).
    • Added a Telegram support channel reference.
    • Clarified bonding pool context in onboarding guide.
    • Updated the list of supported blockchain networks in endpoint documentation.

✏️ Tip: You can customize this high-level summary in your review settings.

Updated sidebar position and added notes regarding the bonding pool.
@tamir-cow tamir-cow requested a review from a team as a code owner November 26, 2025 08:36
@vercel
Copy link

vercel bot commented Nov 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
docs Ready Ready Preview Nov 26, 2025 8:48am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 26, 2025

Warning

Rate limit exceeded

@tamir-cow has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 38 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between aed7925 and 6ad6d28.

📒 Files selected for processing (1)
  • docs/cow-protocol/reference/core/auctions/schema.md (1 hunks)

Walkthrough

Updated documentation in the solvers tutorials: marked from_shadow_to_prod as draft, adjusted sidebar ordering for onboard/local_test/routes_integration, and added Telegram note, bonding-pool clarification, and a supported-networks list in the onboard guide.

Changes

Cohort / File(s) Summary
Shadow → Prod tutorial (metadata)
docs/cow-protocol/tutorials/solvers/from_shadow_to_prod.md
Added draft: true to YAML front matter; no other content changes.
Onboarding doc (content & metadata)
docs/cow-protocol/tutorials/solvers/onboard.md
Changed sidebar_position (5 → 1); added a Telegram note, bonding-pool clarification, and supported networks list (arbitrum-one, avalanche, base, bnb, lens, linea, mainnet, polygon, xdai (gnosis), others forthcoming).
Local test & routes integration (metadata)
docs/cow-protocol/tutorials/solvers/local_test.md, docs/cow-protocol/tutorials/solvers/routes_integration.md
Updated sidebar_position values (local_test.md 1 → 2; routes_integration.md 2 → 3); no content changes.

Sequence Diagram(s)

(No sequence diagrams: changes are documentation/front-matter edits only.)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Review focuses on front-matter correctness and small content additions in onboard.md.
  • Pay attention to the supported networks list formatting and placement of the Telegram and bonding-pool notes.

Possibly related PRs

Suggested reviewers

  • harisang
  • bram-vdberg
  • MartinquaXD

Poem

🐰 I hopped through front-matter, neat and spry,
I nudged the sidebar, gave networks a try,
A Telegram note, a bonding clue,
Drafted a guide, shiny and new —
Hooray, docs ready! 🌿✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main changes: sidebar position updates and enhancement of onboarding notes with bonding pool information.
Description check ✅ Passed The description adequately explains the changes and key context (sidebar position updates, bonding pool notes, and removal of from_shadow_to_prod from sidebar), but does not fully follow the template structure with a dedicated Changes section.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7408f18 and 0bb6ec9.

📒 Files selected for processing (2)
  • docs/cow-protocol/tutorials/solvers/from_shadow_to_prod.md (2 hunks)
  • docs/cow-protocol/tutorials/solvers/onboard.md (2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/cow-protocol/tutorials/solvers/onboard.md

[style] ~6-~6: Consider a more concise word here.
Context: ...otocol Solver Competition > NOTE: In order to get connected to the shadow competition...

(IN_ORDER_TO_PREMIUM)

🪛 markdownlint-cli2 (0.18.1)
docs/cow-protocol/tutorials/solvers/onboard.md

7-7: Blank line inside blockquote

(MD028, no-blanks-blockquote)

🔇 Additional comments (3)
docs/cow-protocol/tutorials/solvers/from_shadow_to_prod.md (1)

3-3: Draft marking is appropriate.

Marking this shadow-to-production tutorial as draft aligns with ongoing development and allows readers to understand this is guidance under refinement.

docs/cow-protocol/tutorials/solvers/onboard.md (2)

2-2: Sidebar reordering elevates the onboarding guide appropriately.

Moving sidebar_position from 5 to 1 makes this foundational guide the first in the solvers tutorial sequence, which is contextually correct for solver onboarding.


45-49: Network support transparency is helpful.

The addition of the supported networks list at line 48 clearly communicates availability and sets expectations for solvers. The list is informative and well-placed in the Exposed Endpoint section.

Comment on lines +6 to 8
> **_NOTE:_** In order to get connected to the shadow competition, feel free to reach out to an admin of the ["CoW Swap Solvers"](https://t.me/+2Z_-DW57meA1MDlh) group on Telegram.
> **_NOTE:_** Most of this document assumes that you will be joining the solver competition under the CoW DAO bonding pool. If you were to set up your own bonding pool then most of the information in this document is either optional or irrelevant. To join the solver competition under your own bonding pool refer to [this document](https://docs.cow.fi/cow-protocol/reference/core/auctions/bonding-pools) and reach out to help set up the bonding pool and whitelist your solver's address.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix blockquote formatting and simplify phrase.

Line 7 creates a blank line inside the blockquote, which violates markdown block integrity (MD028). Additionally, "In order to" at line 6 can be simplified to "To" for conciseness.

Apply this diff to fix the formatting and improve clarity:

  # Joining The CoW Protocol Solver Competition
- > **_NOTE:_** In order to get connected to the shadow competition, feel free to reach out to an admin of the ["CoW Swap Solvers"](https://t.me/+2Z_-DW57meA1MDlh) group on Telegram.
-
+ > **_NOTE:_** To get connected to the shadow competition, feel free to reach out to an admin of the ["CoW Swap Solvers"](https://t.me/+2Z_-DW57meA1MDlh) group on Telegram.
  > **_NOTE:_** Most of this document assumes that you will be joining the solver competition under the CoW DAO bonding pool...
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
> **_NOTE:_** In order to get connected to the shadow competition, feel free to reach out to an admin of the ["CoW Swap Solvers"](https://t.me/+2Z_-DW57meA1MDlh) group on Telegram.
> **_NOTE:_** Most of this document assumes that you will be joining the solver competition under the CoW DAO bonding pool. If you were to set up your own bonding pool then most of the information in this document is either optional or irrelevant. To join the solver competition under your own bonding pool refer to [this document](https://docs.cow.fi/cow-protocol/reference/core/auctions/bonding-pools) and reach out to help set up the bonding pool and whitelist your solver's address.
> **_NOTE:_** To get connected to the shadow competition, feel free to reach out to an admin of the ["CoW Swap Solvers"](https://t.me/+2Z_-DW57meA1MDlh) group on Telegram.
> **_NOTE:_** Most of this document assumes that you will be joining the solver competition under the CoW DAO bonding pool. If you were to set up your own bonding pool then most of the information in this document is either optional or irrelevant. To join the solver competition under your own bonding pool refer to [this document](https://docs.cow.fi/cow-protocol/reference/core/auctions/bonding-pools) and reach out to help set up the bonding pool and whitelist your solver's address.
🧰 Tools
🪛 LanguageTool

[style] ~6-~6: Consider a more concise word here.
Context: ...otocol Solver Competition > NOTE: In order to get connected to the shadow competition...

(IN_ORDER_TO_PREMIUM)

🪛 markdownlint-cli2 (0.18.1)

7-7: Blank line inside blockquote

(MD028, no-blanks-blockquote)

🤖 Prompt for AI Agents
In docs/cow-protocol/tutorials/solvers/onboard.md around lines 6 to 8, the
blockquote contains a blank line that breaks markdown block integrity and the
phrase "In order to" is verbose; remove the empty line between the two NOTE
paragraphs so the blockquote remains continuous and replace "In order to get
connected to the shadow competition" with "To get connected to the shadow
competition" to simplify the wording.

Updated the reference to API specification and schema.
@harisang harisang merged commit 4a7bddf into main Nov 28, 2025
6 checks passed
@harisang harisang deleted the enhancements/solver-docs branch November 28, 2025 12:45
@github-actions github-actions bot locked and limited conversation to collaborators Nov 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants