Skip to content

Archive repository and provide new location link#19

Open
MatteoDelOmbra wants to merge 1 commit intomainfrom
archive-repo
Open

Archive repository and provide new location link#19
MatteoDelOmbra wants to merge 1 commit intomainfrom
archive-repo

Conversation

@MatteoDelOmbra
Copy link
Copy Markdown
Contributor

@MatteoDelOmbra MatteoDelOmbra commented Mar 31, 2026

Summary by CodeRabbit

  • Documentation
    • Repository is now archived and no longer actively maintained. Development has been migrated to a new GitHub location, with documentation updated to include a link to the new repository for continued access.

Indicate that the repository is archived and no longer supported, with a link to the new location for ongoing development.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 31, 2026

Walkthrough

The pull request adds an "ARCHIVED" notice to the README.md file, indicating the repository is no longer actively maintained. The notice includes information that the codebase has been migrated and provides a link to the new GitHub repository location for continued development.

Changes

Cohort / File(s) Summary
Documentation
README.md
Added archived notice at the top indicating the repository is no longer maintained, with migration details and a link to the new GitHub location.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A repository rests, its purpose now past,
Archived with care, though the sprint wasn't last,
Fear not, dear readers, the work carries on,
At a new home, where the future's not gone! 🏠✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately describes the main change: adding an archived notice and migration link to README.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch archive-repo

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 5: The heading "### 🚀 New Location" jumps from a higher-level '#' header
and triggers MD001; change that line to "## 🚀 New Location" (or insert an
intermediate "##" section above and keep this as "###") so the README heading
hierarchy is sequential and satisfies Markdown linting.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8dbbc32b-9a02-44c9-8ecf-6dc1b1559697

📥 Commits

Reviewing files that changed from the base of the PR and between 6ff69ac and 8378fb1.

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


This repository is **no longer actively maintained or supported**. The codebase has been migrated to a new location to ensure better integration and ongoing updates.

### 🚀 New Location
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix heading level jump (####) to satisfy Markdown lint.

Line 5 should use ## (or add an intermediate ## section) to avoid MD001 and keep heading hierarchy valid.

Suggested fix
-### 🚀 New Location
+## 🚀 New Location
📝 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
### 🚀 New Location
## 🚀 New Location
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)

[warning] 5-5: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 5, The heading "### 🚀 New Location" jumps from a
higher-level '#' header and triggers MD001; change that line to "## 🚀 New
Location" (or insert an intermediate "##" section above and keep this as "###")
so the README heading hierarchy is sequential and satisfies Markdown linting.

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.

1 participant