docs: deprecation notice

[MDr164]

Summary by CodeRabbit

• Documentation
  • Marked the project as deprecated with a prominent notice directing users to the main u-bmc repository.
  • Clarified that, while standalone builds are possible, this tool is intended to be built and bundled via the u-bmc build process.
  • No code, functionality, or public API changes; usage remains unaffected.

[coderabbitai]

Walkthrough

Documentation-only update: README.md now includes a deprecation notice pointing to the main u-bmc/u-bmc repository and clarifies that this tool is intended to be built via the u-bmc build process. No code or API changes.

Changes

Cohort / File(s)	Summary of Changes
Documentation README.md	Added DEPRECATED block after title; clarified build context (standalone vs bundled by u-bmc); no code/public API modifications; license badge unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I thump my paws: “Deprecated, see!”
A README signpost under the tree.
Follow the trail to u-bmc’s den,
Where builds are bundled now and then.
I nibble docs with tidy delight—
Carrots for clarity, crisp and bright.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch notice

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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)

3-6: Optional: Add date and issue/PR guidance to the deprecation block.

This reduces ambiguity for users landing here and helps route support correctly.

Apply this diff to enrich the message:

-> **DEPRECATED**
+> **DEPRECATED**
 >
-> This repository is deprecated. All current development has moved to the main [u-bmc/u-bmc](https://github.com/u-bmc/u-bmc) repository.
+> This repository is deprecated as of August 2025. All current development has moved to the main [u-bmc/u-bmc](https://github.com/u-bmc/u-bmc) repository. Issues and pull requests are not monitored here; please use [u-bmc/u-bmc issues](https://github.com/u-bmc/u-bmc/issues).

Additional nice-to-haves (no doc changes required here):

• Add a “Deprecated” or “No longer maintained” badge next to the license badge.
• Consider archiving the repository in GitHub settings to prevent new issues/PRs.

If you want, I can draft the badge snippet and an ISSUE_TEMPLATE note that points users to u-bmc/u-bmc.

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 20fd61e and 286d4e8.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: coverage
• GitHub Check: race

🔇 Additional comments (1)

README.md (1)

3-6: Deprecation notice reads clearly and is well-placed.

Good use of a prominent blockquote at the top to steer users to the active repository. No blocking issues.