Skip to content

Commit ca0ea5d

Browse files
author
Sean Wheeler
committed
update templates
1 parent 84e97df commit ca0ea5d

File tree

6 files changed

+139
-25
lines changed

6 files changed

+139
-25
lines changed

‎.github/ISSUE_TEMPLATE.md

Lines changed: 0 additions & 25 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/Code_Bug_Report.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: Code Bug Report 🐛
3+
about: PowerShell behavior issues should be filed in the [PowerShell](https://github.com/PowerShell/PowerShell/issues/new) code repository
4+
title: Issue title
5+
labels: issue-product-feedback
6+
assignees: ''
7+
8+
---
9+
10+
# Product Issue
11+
12+
If this issue is that the behavior is documented incorrectly then use the **Doc Bug Report**
13+
template. Otherwise, issues about PowerShell behavior should be filed in the
14+
[PowerShell](https://github.com/PowerShell/PowerShell/issues/new/choose) code repository.

‎.github/ISSUE_TEMPLATE/Documentation_Issue.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
name: Documentation Issue 📚
3+
about: Problems with PowerShell documentation
4+
title: "Documentation Issue"
5+
labels: issue-question
6+
assignees: ''
7+
8+
---
9+
10+
# Documentation Issue
11+
12+
<!--
13+
Use this template to report issues with documentation. This can include typos, technical and factual
14+
errors, grammar, spelling, formatting, presentation, etc.
15+
16+
Be sure to change the issue title. Titles should be brief and meaningful.
17+
-->
18+
19+
## Details of the issue
20+
21+
- URL to the article (Docs or GitHub URL):
22+
- Is the issue version specific (Y/N - include version info) :
23+
- [ ] Impacts 7 document
24+
- [ ] Impacts 6 document
25+
- [ ] Impacts 5.1 document
26+
- [ ] Impacts 5.0 document
27+
- [ ] Impacts 4.0 document
28+
- [ ] Impacts 3.0 document
29+
- Is the issue specific to a platform (Y/N - Win/macOS/Linux):
30+
31+
Description of the issue:
32+
33+
<!--
34+
Enter your problem description below. Use markdown code fences for example code and output.
35+
-->

‎.github/ISSUE_TEMPLATE/New_Document_Request.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: New Document Request/Idea 🚀
3+
about: Suggest a new document or major rewrite of an existing one
4+
title: "Document Request"
5+
labels: issue-doc-idea
6+
assignees: ''
7+
8+
---
9+
10+
# Summary of the new document or enhancement
11+
12+
<!--
13+
A clear and concise description of purpose the new document. Why it is needed? What gap is it
14+
filling? Who is the intended audience? What is the intended scenario being addressed?
15+
16+
Try formulating it in user story style (if applicable):
17+
18+
'As a user I need a document about X so that I can Y.' with X being the problem or scenario and Y
19+
being the purpose and/or target audience for the document.
20+
21+
Be sure to change the issue title. Titles should be brief and meaningful.
22+
-->
23+
24+
Details of requested document:
25+
26+
- Proposed title:
27+
- Propose location in the TOC:
28+
- Target audience:
29+
- Purpose or scenario:
30+
_or_
31+
Proposed changes/additions to existing article:
32+
- List of related articles to link to:

‎.github/ISSUE_TEMPLATE/Support_Question.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
name: Support Question ❓
3+
about: If you have a question, you can try asking in the PowerShell Slack channel first. If you need official support, refer to the [PowerShell Support Lifecycle](https://aka.ms/pslifecycle)
4+
title: "Support Question"
5+
labels: issue-question
6+
assignees: ''
7+
8+
---
9+
10+
# Support Question
11+
12+
## Official support
13+
14+
[PowerShell Support Lifecycle](https://aka.ms/pslifecycle)
15+
16+
## Community Resources
17+
18+
[Slack][powershell-slack] and [Discord][powershell-discord] Community Chat - Interactive chat with
19+
other PowerShell enthusiasts. Both Slack and Discord are bridged via a bot and can seamlessly talk
20+
to each other.
21+
22+
[StackOverflow.com](https://stackoverflow.com/questions/tagged/powershell) and
23+
[PowerShell.org Forum](https://powershell.org/forums/) - Search or post new general PowerShell usage
24+
questions.
25+
26+
[powershell-slack]: https://join.slack.com/t/powershell/shared_invite/enQtMzA3MDcxNTM5MTkxLTBmMWIyNzhkYzVjNGRiOTgxZmFlN2E0ZmVmOWU5NDczNTY2NDFhZjFlZTM1MTZiMWIzZDcwMGYzNjQ3YTRkNWM
27+
[powershell-discord]: https://discordapp.com/invite/AtzXnJM

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,34 @@ Reason(s) for not updating all version of documents
2121
- [ ] The documented feature was introduced in version (list version here) of PowerShell
2222
- [ ] This issue only shows up in version (list version(s) here) of the document
2323
- [ ] This PR partially fixes the issue, and issue #<insert here> tracks the remaining work
24+
25+
26+
<!-- Anything that looks like this is a comment and can't be seen after the Pull Request is created. -->
27+
28+
# PR Summary
29+
30+
<!-- Summarize your changes and list related issues here -->
31+
32+
33+
## PR Context
34+
35+
Version(s) of documents impacted
36+
------------------------------
37+
- [ ] Impacts 7 document
38+
- [ ] Impacts 6 document
39+
- [ ] Impacts 5.1 document
40+
- [ ] Impacts 5.0 document
41+
- [ ] Impacts 4.0 document
42+
- [ ] Impacts 3.0 document
43+
44+
## PR Checklist
45+
46+
- [ ] I have read the [contributors guide(https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/CONTRIBUTING.md)]
47+
and followed the style and process guidelines
48+
- [ ] PR has a meaningful title
49+
- [ ] PR is targetted at the _staging_ branch
50+
- [ ] All relevant versions updated
51+
- [ ] Includes reference to related issues and PRs - see [Closing issues using keywords](https://help.github.com/en/articles/closing-issues-using-keywords).
52+
- [ ] This PR is ready to merge and is not **Work in Progress**
53+
- If the PR is work in progress, please add the prefix `WIP:` or `[ WIP ]` to the beginning of the
54+
title and remove the prefix when the PR is ready.

0 commit comments

Comments
 (0)