docs: navigating section links path

[guspan-tanadi]

Summary by CodeRabbit

• Documentation
  • Updated the documentation link in the subgraph guide to ensure users access the latest instructions for writing mappings.
  • Refreshed the link in the environment configuration guide to direct users to the current setup details for the service.

[coderabbitai]

Walkthrough

The changes update URLs in two README files. In the subgraph-writer documentation, the link guiding users on writing mappings has been updated to reflect the new documentation structure. Similarly, the User Ops Indexer README now directs users to the updated configuration documentation for Blockscout instance environment variables. Both updates ensure that users are pointed to the correct and current resources. No other modifications or alterations to exported or public entities were made.

Poem

I'm a rabbit hopping in code,
Celebrating links in their new abode!
Old URLs out, new guides in play,
Leading the way in a bright, fresh way.
Hop along and code with glee,
Updates set our docs truly free!
🐰✨

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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: 0

🧹 Nitpick comments (1)

blockscout-ens/graph-node/subgraph-writer/README.md (1)

43-43: Validate the updated URL and consider text brevity for clarity.

The updated URL now points to the correct and current official subgraph guide (https://thegraph.com/docs/en/subgraphs/developing/creating/assemblyscript-mappings/#writing-mappings), ensuring that users are directed to the appropriate resource. Additionally, as noted by LanguageTool, you might consider shortening or rephrasing the sentence to enhance readability and reduce wordiness.

🧰 Tools

🪛 LanguageTool

[style] ~43-~43: Consider a shorter alternative to avoid wordiness.
Context: ...handle events of your protocol properly in order to index all blockchain data. You can use ...

(IN_ORDER_TO_PREMIUM)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a7571da and 33059ed.

📒 Files selected for processing (2)

• blockscout-ens/graph-node/subgraph-writer/README.md (1 hunks)
• user-ops-indexer/README.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• user-ops-indexer/README.md

🧰 Additional context used

🪛 LanguageTool

blockscout-ens/graph-node/subgraph-writer/README.md

[style] ~43-~43: Consider a shorter alternative to avoid wordiness.
Context: ...handle events of your protocol properly in order to index all blockchain data. You can use ...

(IN_ORDER_TO_PREMIUM)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Docker build and docker push / build-and-push
• GitHub Check: Linting / lint
• GitHub Check: Unit, doc and integration tests