microsoft / microsoft/documentdb-mcp
[DX] Set up GitHub Discussions templates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 3
Description
Goal
Reduce low-quality issues; route conversations to the right place.
What to ship
Discussion templates (since Discussions is enabled on the repo):
I'm trying to do X(help / how-to)Bug report(bug)Feature request(idea)Show & tell(community)
Issue templates already exist for bugs; clarify when to file an issue vs. start a discussion.
Acceptance criteria
- Templates live in
.github/DISCUSSION_TEMPLATE/. - README links to Discussions for help / questions.
- CONTRIBUTING.md is updated to clarify the issue-vs-discussion split.
Why
Low-effort, high-leverage hygiene. Keeps the issue tracker focused on actionable work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing issue templates and the repository README and CONTRIBUTING.md, then check how GitHub Discussions is configured. Add the four templates under .github/DISCUSSION_TEMPLATE/ and clarify the issue-versus-discussion split in README and CONTRIBUTING.md; done means all acceptance criteria are present and the links and guidance are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100