fix(article): Fix Typo in Supervive Blog URLs

[infinia-yzl]

Fixes: #113

Description

Fixes typos in tier list URLs in the article.

Summary by CodeRabbit

• New Features
  • Updated URLs for the tier lists of hunters in the SUPERVIVE game, enhancing accessibility to the latest rankings for both new players and tryhards.
• Documentation
  • Revised the supervive-open-beta-guide.md to reflect the changes in URLs while maintaining the overall content structure and formatting.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
opentierboy	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 20, 2024 8:20am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates the supervive-open-beta-guide.md document by modifying the URLs for the tier lists of hunters in the game SUPERVIVE. The changes specifically involve updating the URLs for both beginner and tryhard hunter tier lists to reflect new state parameters. The overall structure and formatting of the document remain unchanged.

Changes

File	Change Summary
articles/supervive-open-beta-guide.md	Updated URLs for the "Hunters for BEGINNERS" and "Hunters for TRYHARDS" tier lists to new state parameters.

Assessment against linked issues

Objective	Addressed	Explanation
Fix typo in Supervive Blog URLs (#113)	✅

Possibly related PRs

• asset(article): Add Supervive Open Beta Blog Article #112: Updates the same document, supervive-open-beta-guide.md, to include a comprehensive tier list for hunters in SUPERVIVE, which relates to the URL updates in this PR.

🐰 In the land of SUPERVIVE, where hunters roam free,
URLs updated, oh what a spree!
For beginners and tryhards, the lists now align,
With fresh links to guide them, all will be fine!
Hop along, dear players, to the new tiered delight,
Adventure awaits in the moonlit night! 🌙✨

Warning

Rate limit exceeded

@infinia-yzl has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 7 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 66618e8 and 5b657b2.

---

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.

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.