Update readme ss

[cp-sidhdhi-p]

Summary by CodeRabbit

• Documentation
  • Updated README screenshots and headings
  • Reorganized documentation layout
  • Added new sections for Home Screen and Matches List
  • Introduced a new table for Squad and Tournament Detail
  • Improved overall documentation clarity and structure

[coderabbitai]

Warning

Rate limit exceeded

@cp-sidhdhi-p has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 15 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 d49ba65 and 0024bf5.

⛔ Files ignored due to path filters (8)

• screenshots/screen_shot_1.png is excluded by !**/*.png
• screenshots/screen_shot_2.png is excluded by !**/*.png
• screenshots/screen_shot_3.png is excluded by !**/*.png
• screenshots/screen_shot_4.png is excluded by !**/*.png
• screenshots/screen_shot_5.png is excluded by !**/*.png
• screenshots/screen_shot_6.png is excluded by !**/*.png
• screenshots/screen_shot_7.png is excluded by !**/*.png
• screenshots/screen_shot_8.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md (3 hunks)

Walkthrough

The pull request updates the README.md file, specifically enhancing the organization of the screenshots section. It involves changing the heading "Matches Record" to "Home Screen," adding a new heading "Matches List," and moving the "Start New Match" heading to a new table. The "Squad" heading has been removed, and a new table featuring "Squad" and "Tournament Detail" headings has been introduced. These changes improve the clarity and structure of the documentation.

Changes

File	Change Summary
README.md	- Replaced "Matches Record" heading with "Home Screen" - Added new "Matches List" heading - Moved "Start New Match" heading to a new table - Removed "Squad" heading from the previous table - Introduced new table with "Squad" and "Tournament Detail" headings and their respective screenshots

Possibly related PRs

• Update screenshots #109: This PR involves updates to the README.md file, including formatting improvements and adjustments to the screenshots section, which aligns with the main PR's focus on reorganizing and enhancing the screenshots section.
• Fix contribution numbering #158: This PR also updates the README.md file, specifically adding a "Tournament Feature" to the list of features, which relates to the overall documentation structure and user interface enhancements mentioned in the main PR.

Suggested reviewers

• cp-mayank

Poem

🐰 A README tale of screenshots bright,
Headings dancing with rabbit-like might!
Rearranged with a hop and a glee,
Clarity blooms like a digital tree 📱
Docs now sparkle, oh so clean! 🌟

---

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)

README.md (1)

45-54: Consider maintaining visual consistency across tables.

While the new table effectively organizes related screenshots, consider these suggestions to maintain visual consistency:

1. Add a third screenshot to match the layout of other tables, or
2. Adjust the width distribution (e.g., to 45% each) to better utilize the space with two columns.

If you choose option 2, here's the suggested change:

-    <th width="32%">Squad</th>
-    <th width="32%">Tournament</th>
+    <th width="45%">Squad</th>
+    <th width="45%">Tournament</th>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d0e8d30 and 50e01dd.

⛔ Files ignored due to path filters (8)

• screenshots/screen_shot_1.png is excluded by !**/*.png
• screenshots/screen_shot_2.png is excluded by !**/*.png
• screenshots/screen_shot_3.png is excluded by !**/*.png
• screenshots/screen_shot_4.png is excluded by !**/*.png
• screenshots/screen_shot_5.png is excluded by !**/*.png
• screenshots/screen_shot_6.png is excluded by !**/*.png
• screenshots/screen_shot_7.png is excluded by !**/*.png
• screenshots/screen_shot_8.png is excluded by !**/*.png

📒 Files selected for processing (1)

• README.md (3 hunks)

🔇 Additional comments (2)

README.md (2)

21-22: LGTM! Clear and consistent heading updates.

The new headings "Home Screen" and "Matches" provide better clarity about the screenshot contents.

---

34-34: LGTM! Logical reorganization of match-related screenshots.

The placement of "Start New Match" in this section creates a better flow with other match-related screenshots.