docs: Migrate all references to our old community Slack to the new GitHub Discussions

[UncannyBingo]

…iscussions

[coderabbitai]

Walkthrough

Replaced the Slack badge/link in the README header with a GitHub Discussions badge/link. No other content changes.

Changes

Cohort / File(s)	Summary of changes
Docs README.md	Updated header badge: replaced Slack with GitHub Discussions, updating link target accordingly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A badge hops left, a link hops right,
I twitch my whiskers—forums in sight.
Slack says bye, Discussions say hi,
A tidy tweak beneath the sky.
Thump-thump approves, with paws so light.

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 migrate-slack-to-github

---

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 (2)

README.md (2)

1-1: Confirm target: org-level vs repo-level Discussions

If the intent is to funnel users into this repository’s discussions (rather than the organization-wide board), consider linking to the repo-level page. The badge image already references the stack repo, so only the href needs adjustment.

Apply this minimal change:

-[![GitHub Discussions](https://img.shields.io/github/discussions/formancehq/stack)](https://github.com/orgs/formancehq/discussions)
+[![GitHub Discussions](https://img.shields.io/github/discussions/formancehq/stack)](https://github.com/formancehq/stack/discussions)

---

1-1: Stars badge and License link currently point to the ledger repository

Since this is the stack README, consider pointing the “Stars” badge and “License” link to this repo for consistency and to avoid user confusion.

Proposed inline fixes:

-[![Ledger Stars](https://img.shields.io/github/stars/formancehq/ledger?label=Ledger%20stars)](https://github.com/formancehq/ledger/stargazers) [![License MIT](https://img.shields.io/badge/license-mit-purple)](https://github.com/formancehq/ledger/blob/main/LICENSE)
+[![Stack Stars](https://img.shields.io/github/stars/formancehq/stack?label=Stack%20stars)](https://github.com/formancehq/stack/stargazers) [![License MIT](https://img.shields.io/badge/license-mit-purple)](https://github.com/formancehq/stack/blob/main/LICENSE)

If you purposefully highlighted Ledger’s popularity/license, feel free to ignore this.

📜 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 1c5d03e and 43d9835.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (2)

README.md (2)

1-1: LGTM: Slack → GitHub Discussions badge/link migrated correctly

The replacement to a Discussions badge is accurate and the target points to the org-level discussions. No syntax issues found.

---

1-1: Sweep complete – no Slack references detected

I ran the provided ripgrep command across the entire repository and confirmed zero occurrences of “slack” (case-insensitive) in code, docs, examples, or links. All Slack references have been removed.