docs: update links to sync_service.go

[tzdybal]

Overview

After the block_sync.go and header_sync.go was removed (merged into sync_service.go, links in .md files are dead.

Summary by CodeRabbit

• Documentation
  • Updated descriptions in README to emphasize Rollkit's role in launching customizable blockchains.
  • Fixed broken links in block-manager.md and header-sync.md to point to the correct sync service files.
  • Adjusted file paths for Header Sync Service and Block Sync Service links in full_node.md.

[coderabbitai]

Walkthrough

Recent updates involve documentation enhancements and path corrections, specifically adjusting references to the header and block sync services in multiple Markdown files. These revisions enhance the accuracy and clarity of documentation related to Rollkit's functionality without altering any public or exported entities.

Changes

File	Change Summary
README.md	Adjusted the description to highlight Rollkit's role as a customizable blockchain framework.
block/block-manager.md	Updated the [block-sync] link from block_sync.go to sync_service.go.
block/header-sync.md	Updated header sync references and links from header_sync.go to sync_service.go.
node/full_node.md	Changed the file paths for Header Sync Service and Block Sync Service links to sync_service.go.

Poem

In the code's vast warren, paths realign,
Links now properly intertwine.
Rollkit's tale, told anew,
From block to header, clear in view.
Sync services glide, smooth and bright,
Documented paths, setting right.

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between e43f6da and 3a88046.

Files selected for processing (4)

• README.md (1 hunks)
• block/block-manager.md (1 hunks)
• block/header-sync.md (1 hunks)
• node/full_node.md (1 hunks)

Files skipped from review due to trivial changes (3)

• README.md
• block/header-sync.md
• node/full_node.md

Additional comments not posted (1)

block/block-manager.md (1)

188-188: Update link to sync_service.go

The link [block-sync] has been correctly updated to point to sync_service.go.