GitHub Discussions and Community Support Guidelines
Plan how questions and ideas are handled outside issues.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan GitHub Discussions for [PROJECT]. Community size and activity: [COMMUNITY]. Types of posts: [POST_TYPES]. Maintainer time: [MAINTAINER_TIME]. Problems with questions in issues: [PROBLEMS]. Propose categories, rules, a code of conduct summary, and moderation steps. Write the welcome post in full, about 120 words, warm and direct. Give five short rules, a plain explanation of what belongs in discussions versus issues, and a polite template for moving a post from one to the other. Add three levels of moderation response with example wording: a friendly reminder, a firm warning, and removal. Include reply templates for common situations, how to recognise helpful members, and how to handle unkind behaviour. Suggest a weekly 20-minute routine: answer unanswered questions, thank helpers, convert good ideas into issues, and review reports. Measure time to first reply and the share of questions answered, and respect the limits of volunteer time. Check feature availability [VERIFY]. Keep every template short enough to adapt in a minute. Say what to do first if only one maintainer has time this week, and what to stop doing if the community grows.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.