Update README.md

[Vad1mo]

docs: add debug images into the list of next

Summary by CodeRabbit

• Documentation
  • Added a new section titled "Harbor Next Differences" to clarify features of the Harbor Next version.
  • Updated the feature list to include "Debug" under multiple flavors.
  • Enhanced the description of Harbor Next with stability and backward compatibility information.
  • Included details on community engagement and bi-weekly calls.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to the README.md file of the Harbor project. It adds a new section titled "Harbor Next Differences," detailing specific features of the Harbor Next version, including multiple flavors and capabilities such as continuous delivery. The feature list has been updated to reflect the addition of "Debug" to the flavors. The description of Harbor Next has been enhanced to emphasize stability, backward compatibility, and community engagement, while the overall structure of the document remains unchanged.

Changes

File	Change Summary
README.md	- Added "Harbor Next Differences" section.
	- Updated feature list to include "Debug" in "Multiple flavors."
	- Enhanced description of Harbor Next regarding stability and community engagement.

Possibly related PRs

• Update README.md #48: This PR also modifies the README.md file, specifically adding a section on the differences of Harbor Next and updating features related to community engagement and project description, which aligns closely with the changes made in the main PR.

---

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. (Experiment)
• @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

🧹 Outside diff range and nitpick comments (1)

README.md (1)

33-33: Consider adding documentation for the Debug flavor

While adding "Debug" to the list of flavors is aligned with the PR objectives, it would be helpful to provide additional context about:

• What the Debug flavor includes
• When users should choose this flavor over others
• Any specific use cases or limitations

This will help users make informed decisions about which flavor best suits their needs.

Consider adding a subsection that briefly describes each flavor:

### Available Flavors
- **Vanilla**: Standard Harbor installation
- **Next**: Enhanced version with upcoming features
- **Debug**: [Add description of debug flavor here]

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2feb2dc and 17e415f.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

33-33: LGTM - Change is clear and consistent

The addition of the Debug flavor to the list maintains consistent formatting and integrates well with the existing documentation structure.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud