-
Notifications
You must be signed in to change notification settings - Fork 23
Replace Slack references with GitHub Discussions links #416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ba6b70b to
ae86441
Compare
Preview link: https://www-steeltoe-pr-416.azurewebsites.net
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR migrates the project's community communication channels from Slack to GitHub Discussions, updating references across both the website components and documentation. The change aims to consolidate community engagement around GitHub's native discussion platform.
Changes:
- Updated website components to replace Slack references with GitHub Discussions
- Modified documentation to point users to GitHub Discussions for community support
- Retained one historical Slack reference in an older article to preserve context
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/Steeltoe.io/Components/Pages/Why-Steeltoe.razor | Updated community support description to reference GitHub instead of Slack |
| src/Steeltoe.io/Components/Pages/Support.razor | Removed Slack feature card from support page |
| src/Steeltoe.io/Components/Pages/Community.razor | Replaced Slack section with GitHub Discussions section, including updated icon and description |
| docs/guides/get-to-know-steeltoe/summary.md | Removed Slack from support resource list |
| docs/docs/v4/bootstrap/app-bootstrap.md | Updated feedback section to reference GitHub Discussions instead of Slack |
| docs/docs/v3/bootstrap/index.md | Updated feedback section to reference GitHub Discussions instead of Slack |
| docs/articles/releases/steeltoe-4-0-0-rc1.md | Updated community engagement links to point to GitHub Discussions |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>
…ub Discussions link Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>
Co-authored-by: TimHess <3947063+TimHess@users.noreply.github.com>
Co-authored-by: Bart Koelman <104792814+bart-vmware@users.noreply.github.com>
2bc4463 to
ed3c587
Compare
9c54301 to
d966ec0
Compare
d966ec0 to
9c54301
Compare
Replaces all Slack channel references (slack.steeltoe.io, steeltoeteam.slack.com) with GitHub Discussions links throughout the documentation and website codebase. Other support channels (GitHub, Stack Overflow, Twitter/X, NuGet) remain unchanged.
Changes
Website components:
Support.razor- Replaced Slack feature card with GitHub Discussions feature cardCommunity.razor- Replaced Slack section with GitHub Discussions section including icon, link, and descriptionWhy-Steeltoe.razor- Replaced Slack mention with GitHub Discussions in "Steeltoe is supportive" descriptionDocumentation:
docs/guides/get-to-know-steeltoe/summary.md- Replaced Slack with GitHub Discussions in support listdocs/docs/v3/bootstrap/index.md- Replaced Slack with GitHub Discussions in feedback sectiondocs/docs/v4/bootstrap/app-bootstrap.md- Replaced Slack with GitHub Discussions in feedback sectiondocs/articles/releases/steeltoe-4-0-0-rc1.md- Replaced Slack reference with GitHub Discussions linkdocs/articles/steeltoe-3-2-2-adds-kube-service-bindings.md- Retained original Slack reference to preserve historical contextBefore:
After:
All Slack references now point to GitHub Discussions (https://github.com/SteeltoeOSS/Steeltoe/discussions), providing users with an active, supported community engagement channel.
Original prompt
This pull request was created from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.