feat: add issue templates, discussion templates, and PR template#4
Merged
Merged
feat: add issue templates, discussion templates, and PR template#4
Conversation
Issue templates (YAML forms): - bug_report.yml: PS version + OS dropdowns, module version, repro, logs - feature_request.yml: problem/solution/alternatives, contribution dropdown - question.yml: short form redirecting to Discussions - tool_adoption_request.yml: full adoption front-door form - config.yml: blank issues disabled, contact links to Discussions and SECURITY.md Discussion templates: announcements, general, ideas PULL_REQUEST_TEMPLATE.md: type checkboxes + psake-based checklist
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack position: 4 of 7
All YAML issue forms, discussion starters, and the PR template. These are inherited by every repo in the org that doesn't define its own.
What's in this PR
Issue templates (YAML forms):
bug_report.yml— PS version dropdown (5.1 / 7.x / Both), OS dropdown, module version, repro (rendered as PowerShell), log output. Auto-labels:bug,needs-triagefeature_request.yml— problem / solution / alternatives / contribution-willingness dropdown. Auto-labels:enhancement,needs-triagequestion.yml— short form; redirects to Discussions before accepting inputtool_adoption_request.yml— full adoption front-door: license dropdown, submitter relationship, author status, post-adoption commitment dropdown. Auto-labels:adoption-request,needs-triageconfig.yml—blank_issues_enabled: false; contact links to Discussions, SUPPORT.md, and SECURITY.mdDiscussion templates: announcements (maintainer-posted), general, ideas (pre-proposal)
PULL_REQUEST_TEMPLATE.md— type checkboxes (bug/feature/breaking/chore) + psake-based checklist (Invoke-psake Analyze,Invoke-psake Test)Council questions
Invoke-psake Analyzethe right command to call out, or should it just say "PSScriptAnalyzer passes"?Base:
pr/03-community— merge PRs 1–3 first.