Add guidelines for using GitHub Discussions in CONTRIBUTING.md#10
Add guidelines for using GitHub Discussions in CONTRIBUTING.md#10katiesavage wants to merge 1 commit intomainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
Adds contributor-facing guidance on when and how to use GitHub Discussions for community coordination around GitHub Copilot Dev Days, complementing existing contribution resources.
Changes:
- Introduces a new “Using GitHub Discussions” section in
CONTRIBUTING.md - Clarifies when to use Discussions vs. GitHub Issues
- Adds community expectations and a security reporting note
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| If you’ve found a **bug** or have a **specific change request**, please open a **GitHub Issue** so it can be tracked and triaged properly. | ||
|
|
||
| ### Community expectations | ||
| Please help keep this space welcoming and useful: | ||
| - Follow the repository’s [Code of Conduct](/CODE_OF_CONDUCT.md) |
There was a problem hiding this comment.
Within this file, Code of Conduct links are currently relative (e.g., CODE_OF_CONDUCT.md on line 11). Consider making this new link consistent (use the same relative link format) and avoid typographic apostrophes (’), since the rest of CONTRIBUTING.md uses straight apostrophes.
|
|
||
| ### Security note | ||
| Do **not** report security vulnerabilities in Discussions, Issues, or Pull Requests. | ||
| Please follow the process outlined in `SECURITY.md` for responsible disclosure. |
There was a problem hiding this comment.
SECURITY.md is currently formatted as inline code, so it won’t be a clickable link in Markdown. Consider linking it (e.g., [SECURITY.md](SECURITY.md)) for easier navigation.
| Please follow the process outlined in `SECURITY.md` for responsible disclosure. | |
| Please follow the process outlined in [SECURITY.md](SECURITY.md) for responsible disclosure. |
1 participant
No description provided.