|
| 1 | +name: "🛠️ Quality Contribution" |
| 2 | +description: >- |
| 3 | + File a new issue to tackle quality improvement opportunities |
| 4 | +title: "Quality: " |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + This issue template is for the [PowerShell Docs Quality Contributions project][a1]. |
| 10 | + |
| 11 | + For more more info, see [Contributing quality improvements][a2] in our Contributor's Guide. |
| 12 | +
|
| 13 | + [a1]: https://github.com/orgs/MicrosoftDocs/projects/15 |
| 14 | + [a2]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements |
| 15 | + - type: checkboxes |
| 16 | + id: prerequisites |
| 17 | + attributes: |
| 18 | + label: Prerequisites |
| 19 | + description: >- |
| 20 | + These steps are required. After you've completed each step, check the box for it before |
| 21 | + moving on. |
| 22 | + options: |
| 23 | + - label: | |
| 24 | + **Existing Issue:** |
| 25 | +
|
| 26 | + Search the existing [quality issues][b1] for this repository. If there's an issue that |
| 27 | + covers the quality area and articles you want to improve, pick a different quality area |
| 28 | + or article set. Don't file a new issue for the same work. Subscribe, react, or comment |
| 29 | + on that issue instead. |
| 30 | +
|
| 31 | + [b1]: https://github.com/orgs/MicrosoftDocs/projects/15/views/4 |
| 32 | + required: true |
| 33 | + - label: | |
| 34 | + **Descriptive Title:** |
| 35 | +
|
| 36 | + Write the title for this issue as a short synopsis. If possible, provide context. For |
| 37 | + example, "Quality: Command Syntax in Foo" instead of "Quality: Foo" |
| 38 | + required: true |
| 39 | + - type: dropdown |
| 40 | + id: QualityArea |
| 41 | + validations: |
| 42 | + required: true |
| 43 | + attributes: |
| 44 | + label: Quality Areas |
| 45 | + description: | |
| 46 | + Select one or more quality areas to improve on with your contribution. |
| 47 | +
|
| 48 | + For more information, see the relevant section in the meta issue: |
| 49 | +
|
| 50 | + - [Aliases][c1]: Ensure cmdlet aliases are documented |
| 51 | + - [Formatting code samples][c2]: Ensure proper casing, line length, etc in code samples |
| 52 | + - [Formatting command syntax][c3]: Ensure proper casing and formatting for command syntax, including cmdlets, types, etc. |
| 53 | + - [Link References][c4]: Ensure links in conceptual docs are defined as numbered references |
| 54 | + - [Markdown linting][c5]: Ensure content follows markdownlint rules |
| 55 | + - [Spelling][c6]: Ensure proper casing and spelling for words |
| 56 | +
|
| 57 | + [c1]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#aliases |
| 58 | + [c2]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#formatting-code-samples |
| 59 | + [c3]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#formatting-command-syntax |
| 60 | + [c4]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#link-references |
| 61 | + [c5]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#markdown-linting |
| 62 | + [c6]: https://learn.microsoft.com/powershell/scripting/community/contributing/quality-improvements#spelling |
| 63 | + multiple: true |
| 64 | + options: |
| 65 | + - Aliases |
| 66 | + - Formatting code samples |
| 67 | + - Formatting command syntax |
| 68 | + - Link References |
| 69 | + - Markdown linting |
| 70 | + - Spelling |
| 71 | + - type: textarea |
| 72 | + id: ArticleList |
| 73 | + validations: |
| 74 | + required: true |
| 75 | + attributes: |
| 76 | + label: Article List |
| 77 | + description: >- |
| 78 | + Specify the articles you are committing to work on, one per line. You can specify each entry |
| 79 | + as a path, the article's title, or the link to the article on Learn. If you specify an |
| 80 | + article by path for a reference article, such as a cmdlet or about topic, specify the |
| 81 | + version segment as `*.*`. |
| 82 | + placeholder: | |
| 83 | + - reference/*.*/Microsoft.PowerShell.Core/Add-History.md |
| 84 | + - Add-History |
| 85 | + - https://learn.microsoft.com/powershell/module/microsoft.powershell.core/add-history |
0 commit comments