Skip to content

Conversation

@V1d1o7
Copy link
Contributor

@V1d1o7 V1d1o7 commented May 30, 2025

Update License badge to AGPL 3.0

What kind of change does this PR introduce?

eg: Bug fix, feature, docs update, ...

Why was this change needed?

Please link to related issues when possible, and explain WHY you changed things, not WHAT you changed.

Other information:

eg: Did you discuss this change with anybody before working on it (not required, but can be a good idea for bigger changes). Any plans for the future, etc?

Checklist:

Put a "X" in the boxes below to indicate you have followed the checklist;

  • I have read the CONTRIBUTING guide.
  • I checked that there were not similar issues or PRs already open for this.
  • This PR fixes just ONE issue (do not include multiple issues or types of change in the same PR) For example, don't try and fix a UI issue and include new dependencies in the same PR.

Summary by CodeRabbit

  • Documentation
    • Updated the license badge and link in the README to reflect AGPL 3.0 instead of Apache 2.0.

Update License badge to AGPL 3.0
@vercel
Copy link

vercel bot commented May 30, 2025

@V1d1o7 is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented May 30, 2025

Walkthrough

The README.md file was updated to change the displayed license from Apache 2.0 to AGPL 3.0. This included updating the badge image, its alt text, and the hyperlink to point to the AGPL 3.0 license. No other content or files were modified.

Changes

File Change Summary
README.md Updated license badge, alt text, and link from Apache 2.0 to AGPL 3.0

Poem

In README fields where badges gleam,
A license swap—AGPL’s the theme!
From Apache’s shores, we hop anew,
To greener fields and freedoms true.
With every change, a rabbit’s cheer—
🐇 Open code for all to peer!


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
🪧 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
README.md (1)

19-19: Improve alt text for accessibility
Include the license name in the alt attribute to clearly communicate the badge purpose:

-<img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
+<img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License: AGPL v3">
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8314cc5 and cf2564e.

📒 Files selected for processing (1)
  • README.md (1 hunks)

Comment on lines +18 to +19
<a href="https://opensource.org/license/agpl-v3">
<img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix broken AGPL badge link
The OSI license URL should use the plural path licenses and the slug AGPL-3.0 to avoid a 404. Replace:

-<a href="https://opensource.org/license/agpl-v3">
+<a href="https://opensource.org/licenses/AGPL-3.0">
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<a href="https://opensource.org/license/agpl-v3">
<img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
<a href="https://opensource.org/licenses/AGPL-3.0">
<img src="https://img.shields.io/badge/License-AGPL%203.0-blue.svg" alt="License">
🤖 Prompt for AI Agents
In README.md around lines 18 to 19, the AGPL license badge link is broken
because it uses the singular path "license" and an incorrect slug "agpl-v3".
Update the URL to use the plural path "licenses" and the correct slug "AGPL-3.0"
to fix the 404 error.

@nevo-david nevo-david merged commit 9f9eaf9 into gitroomhq:main Jun 10, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants