feat(readme): add a repology badge

[ingenarel]

helps people identify what repos don't or don't have the latest stable version

Summary by CodeRabbit

• Documentation
  • Added a "Packaging status" badge to the README.

[coderabbitai]

Walkthrough

A "Packaging status" badge from Repology was added to the README.md file, positioned after the existing CodeRabbit Pull Request Reviews badge and before the demo image. No other content or formatting in the README was changed.

Changes

File(s)	Change Summary
README.md	Added Repology "Packaging status" badge after the CodeRabbit badge and before the demo image.

Possibly related PRs

• Add codeRabbit badge #743: Also modifies README.md by adding badges, specifically the "CodeRabbit Pull Request Reviews" badge, which is referenced in the current badge placement.

Suggested labels

documentation

Suggested reviewers

• lazysegtree

Poem

A badge hops in, so neat and spry,
"Packaging status" now catches the eye.
Nestled with friends in the README row,
It tells the world how packages grow.
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9016fc6 and 03d812f.

📒 Files selected for processing (1)

• README.md (1 hunks)

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

• README.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[lazysegtree]

@yorukot Please take a look if this is okay.

I kinda dont like so many outdated packages being highlighted in the ReadMe.

Your call.

[yorukot]

@lazysegtree
Are you referring to the entire image, or specifically to the section highlighting the number of outdated packages?
I’m actually opposed to having this image in its current position, as it draws too much attention.

[lazysegtree]

Are you referring to the entire image, or specifically to the section highlighting the number of outdated packages?

section highlighting the number of outdated packages?

I’m actually opposed to having this image in its current position, as it draws too much attention.

Yes. I dont like it either.

Does github readme supports expand boxes ?

Can we do something like this @ingenarel ?

Packaging status

[lazysegtree]

This draws too much attention. Not good for the projects readme. Anyways, packaging it via all package managers is not our goal at this point.

And repology status is already there in the website's page for installation -
https://superfile.netlify.app/getting-started/installation/

[lazysegtree]

@ingenarel Can you go over with above comments and let us know if you still think we need to merge this PR.

[lazysegtree]

No response by 15th Aug, and we will consider this PR stale and close it.