Skip to content

Conversation

@danroth27
Copy link
Member

Clarify that questions and discussions should be handled through GitHub Discussions.

Clarify that questions and discussions should be handled through GitHub Discussions.
@github-actions github-actions bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Dec 18, 2025
Copy link
Contributor

Copilot AI left a 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 updates the CONTRIBUTING.md file to clarify that general questions and discussions should be directed to GitHub Discussions rather than GitHub Issues. The change improves community engagement by steering questions to the appropriate platform and helps keep the issue tracker focused on bugs and feature requests.

Key changes:

  • Updated the section heading from "General feedback and discussions?" to "General questions and discussions?"
  • Redirected users from the repository issue tracker to GitHub Discussions with a more welcoming and descriptive call-to-action

@dotnet-policy-service
Copy link
Contributor

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

@dotnet-policy-service dotnet-policy-service bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Dec 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants