Fix linter error and reorg badges

[madeddie]

User description

Prepare for having a live version badge when deploying to prod pypi

---

PR Type

Bug fix, Documentation

---

Description

• Fixed a linter error in the parse_args function by removing an unused variable.
• Added a new badge for the PyPI test version in the README.
• Reorganized the badges in the README for better readability.

---

Changes walkthrough 📝

	Relevant files
Bug fix	__init__.py Fix linter error in `parse_args` function                                src/tyora/init.py Fixed linter error by removing unused variable parser_login. +1/-1
Documentation	README.md Add PyPI test badge and reorganize badges                                README.md Added a new badge for PyPI test version. Reorganized the badges for better readability. +2/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[coderabbitai]

Warning

Rate Limit Exceeded

@madeddie has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 38 minutes and 37 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

Files that changed from the base of the PR and between 51bd278 and e6f7cac.

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[codiumai-pr-agent-pro]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and limited to a small number of files. The modifications include a simple code cleanup and documentation updates, which are generally easier to review.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[codiumai-pr-agent-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Store the login subparser in a variable for consistency and future reference Consider storing the login subparser in a variable like parser_login as it was before. This can help maintain consistency and make it easier to reference or modify the subparser in the future. src/tyora/init.py [136] -subparsers.add_parser("login", help="Login to mooc.fi CSES") +parser_login = subparsers.add_parser("login", help="Login to mooc.fi CSES") Suggestion importance[1-10]: 8 Why: Reintroducing a variable for the login subparser enhances maintainability and consistency, making future modifications easier.	8
Enhancement	Add a blank line between the badges and the script description for better readability Add a blank line between the badges and the script description to improve readability. README.md [5-8] +[](https://github.com/madeddie/tyora/blob/main/LICENSE) +This script interacts with the mooc.fi instance of the CSES (https://cses.fi) website to perform various actions such as logging in, retrieving exercise lists, and submitting solutions. Suggestion importance[1-10]: 6 Why: Adding a blank line improves the readability of the README, helping to visually separate distinct sections.	6
	Place the new badges on the same line as the existing ones for a cleaner header Move the new badges to be on the same line as the existing ones to maintain a cleaner and more compact header section. README.md [2-3] -[](https://test.pypi.org/project/tyora/) -[](https://github.com/madeddie/tyora/blob/main/pyproject.toml#L15) +[](https://test.pypi.org/project/tyora/) [](https://github.com/madeddie/tyora/blob/main/pyproject.toml#L15) Suggestion importance[1-10]: 5 Why: While placing the badges on the same line improves visual compactness and consistency, it's a minor aesthetic enhancement.	5