chore: Add forum link and remove discord link on readme

[vihar]

Description

• Updated README header navigation: replaced "Releases" link with "Forum" link.
• Removed Discord badge from project documentation.

Type of Change

• Documentation update

[coderabbitai]

📝 Walkthrough

Walkthrough

The README.md file was updated to remove the Discord badge block and the "Releases" link from the header, while adding a new "Forum" link. An empty paragraph was also removed, resulting in a net change of 1 line added and 8 lines removed.

Changes

Cohort / File(s)	Summary
Documentation README.md	Removed Discord badge block and "Releases" link; added new "Forum" link to header; removed trailing empty paragraph.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop, skip, and a link away,
The Discord hops to rest today,
A Forum springs up fresh and bright,
README cleaned with pure delight!
No code to fuss, just text to trim, 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description is minimal and lacks comprehensive detail about the changes, rationale, and testing verification.	Expand the description to include: the specific reason for these documentation changes, any test scenarios performed, and links to related issues if applicable. Consider completing the Type of Change section with an 'x' mark.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main changes: adding a forum link and removing a discord link from the README file.
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 docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-readme

---

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

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

[Copilot]

Pull request overview

Updates the project README’s top navigation/community links to better reflect current community channels.

Changes:

• Removed the Discord badge block from the README header.
• Added a “Forum” link to the top link list.
• Removed the “Releases” link from the top link list.

[Copilot]

The commit-activity badge was removed as part of deleting the Discord badge paragraph. If the intent is only to remove Discord, consider keeping the commit-activity badge (move it into the remaining centered paragraph) or document that this PR also removes the badge.

[Copilot]

The PR title says this change is to add a forum link and remove the Discord link, but this hunk also removes the existing “Releases” link from the top navigation. If removing Releases is intentional, please update the PR title/description; otherwise keep the Releases link and add Forum alongside it.

[Copilot]

This PR removes the Discord badge block, but the README still contains multiple Discord links further down (e.g., the “join the conversation on Discord” callouts). If the goal is to remove Discord links from the README, those references should be updated (e.g., to Forum/GitHub Discussions) or the PR title should be narrowed to only the badge removal.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

README.md (1)

29-29: ⚠️ Potential issue | 🟡 Minor

Residual Discord links inconsistent with the stated PR intent.

The PR title says "remove discord link on readme," but three inline Discord references remain:

• Line 29 — blockquote directing users to Discord for conversation.
• Line 132 — Community section still mentions "our Discord server."
• Line 148 — Contributing section links let us know to the Discord invite URL.

If this PR intentionally only removes the Discord badge/header link (keeping body references), that's fine — but the label [let us know](https://discord.com/invite/A92xrEGCge) on Line 148 is particularly opaque since the Discord destination is not visible to the reader. Consider updating these to point to the Forum or GitHub Discussions, or at minimum making the Discord link label explicit.

Also applies to: 132-132, 148-148

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 29, The README still contains three inline Discord
references that contradict the PR intent: the blockquote "Plane is evolving
every day..." (blockquote directing users to Discord), the Community section
text "our Discord server", and the Contributing link labelled "let us know" that
points to the Discord invite; update these occurrences to either (a) replace the
Discord invite URL with the Forum or GitHub Discussions URL, or (b) change the
link text to explicitly mention "Discord" if you intend to keep it, and
preferably add an alternative destination (Forum/GitHub Discussions) in the same
places; search for the exact phrases "Plane is evolving every day...", "our
Discord server", and the link text "let us know" in README.md and make the
replacements consistently.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@README.md`:
- Line 29: The README still contains three inline Discord references that
contradict the PR intent: the blockquote "Plane is evolving every day..."
(blockquote directing users to Discord), the Community section text "our Discord
server", and the Contributing link labelled "let us know" that points to the
Discord invite; update these occurrences to either (a) replace the Discord
invite URL with the Forum or GitHub Discussions URL, or (b) change the link text
to explicitly mention "Discord" if you intend to keep it, and preferably add an
alternative destination (Forum/GitHub Discussions) in the same places; search
for the exact phrases "Plane is evolving every day...", "our Discord server",
and the link text "let us know" in README.md and make the replacements
consistently.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f534463 and 7fe7c09.

📒 Files selected for processing (1)

• README.md