Skip to content

Conversation

@yedeyu
Copy link

@yedeyu yedeyu commented Dec 2, 2025

Description

This PR adds a missing prerequisite step to the "Option 2: Deploy on Testnet" section.

Changes

  • Added a new ### Get Testnet Tokens section.
  • Clarifies that testnet ZETA is needed for ZetaChain, and specific gas tokens are required to initiate transactions on connected chains (e.g., Base Sepolia).
  • Links to the official documentation containing the list of testnet faucets.

Context

Users following the tutorial previously hit the deployment step without instructions on how to fund their wallets, leading to potential transaction failures due to insufficient gas.

Summary by CodeRabbit

  • Documentation
    • Added guidance for obtaining testnet tokens, including a faucet link reference, to the deployment tutorial section.

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

Added instructions for obtaining testnet tokens
@yedeyu yedeyu requested review from a team as code owners December 2, 2025 01:00
@vercel
Copy link

vercel bot commented Dec 2, 2025

@yedeyu is attempting to deploy a commit to the Zeta Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 2, 2025

📝 Walkthrough

Walkthrough

Documentation update to the "Hello World" tutorial adding a new "Get Testnet Tokens" subsection with guidance and faucet link for obtaining testnet ZETA tokens and gas tokens prior to contract deployment on ZetaChain.

Changes

Cohort / File(s) Summary
Documentation: Testnet Token Acquisition Guidance
src/pages/developers/tutorials/hello.mdx
Added "Get Testnet Tokens" subsection containing token acquisition guidance and faucet link for testnet ZETA and gas tokens. Content inserted before deployment steps to clarify prerequisite token requirements.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Documentation-only changes with no code or logic modifications
  • Straightforward content addition without structural impact
  • Single file affected with consistent formatting

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and specifically describes the primary change: adding testnet token faucet instructions to a deployment guide document.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b2b6791 and eb92b6f.

📒 Files selected for processing (1)
  • src/pages/developers/tutorials/hello.mdx (1 hunks)
🔇 Additional comments (1)
src/pages/developers/tutorials/hello.mdx (1)

234-245: Clear and well-positioned addition addressing a critical prerequisite.

The new "Get Testnet Tokens" section effectively clarifies that users need gas tokens to transact on testnet networks. The explanation logically precedes the deployment steps and is appropriately placed within the Option 2: Deploy on Testnet workflow. The referenced faucet guide is valid and provides access to multiple testnet faucets as intended.


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant