Convert GitHub issue templates to modern forms (#15645)
This commit is contained in:
Andrew Schwartzmeyer
GitHub
parent
1f2dc26ab4
commit
feb6ff396b
47
.github/ISSUE_TEMPLATE/Bug_Report.md
vendored
47
.github/ISSUE_TEMPLATE/Bug_Report.md
vendored
|
|
@ -1,47 +0,0 @@
|
|||
---
|
||||
name: Bug report 🐛
|
||||
about: Report errors or unexpected behavior 🤔
|
||||
title: "My bug report"
|
||||
labels: Needs-Triage
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
<!--
|
||||
|
||||
For Windows PowerShell 5.1 issues, suggestions, or feature requests please use the following link instead:
|
||||
Windows PowerShell [UserVoice](https://windowsserver.uservoice.com/forums/301869-powershell)
|
||||
|
||||
This repository is **ONLY** for PowerShell Core 6 and PowerShell 7+ issues.
|
||||
|
||||
- Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)
|
||||
- Search the existing issues.
|
||||
- Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).
|
||||
- Refer to the [known issues](https://docs.microsoft.com/powershell/scripting/whats-new/known-issues-ps6).
|
||||
|
||||
-->
|
||||
|
||||
## Steps to reproduce
|
||||
|
||||
```powershell
|
||||
|
||||
```
|
||||
|
||||
## Expected behavior
|
||||
|
||||
```none
|
||||
|
||||
```
|
||||
|
||||
## Actual behavior
|
||||
|
||||
```none
|
||||
|
||||
```
|
||||
|
||||
## Environment data
|
||||
|
||||
<!-- provide the output of $PSVersionTable -->
|
||||
|
||||
```none
|
||||
|
||||
```
|
||||
69
.github/ISSUE_TEMPLATE/Bug_Report.yaml
vendored
Normal file
69
.github/ISSUE_TEMPLATE/Bug_Report.yaml
vendored
Normal file
|
|
@ -0,0 +1,69 @@
|
|||
name: Bug report 🐛
|
||||
description: Report errors or unexpected behavior 🤔
|
||||
labels: Needs-Triage
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: >
|
||||
For Windows PowerShell 5.1 issues, suggestions, or feature requests please use the
|
||||
[Windows PowerShell UserVoice](https://windowsserver.uservoice.com/forums/301869-powershell)
|
||||
|
||||
This repository is **ONLY** for PowerShell Core 6 and PowerShell 7+ issues.
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Prerequisites
|
||||
options:
|
||||
- label: Write a descriptive title.
|
||||
required: true
|
||||
- label: Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)
|
||||
required: true
|
||||
- label: Search the existing issues.
|
||||
required: true
|
||||
- label: Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).
|
||||
required: true
|
||||
- label: Refer to the [known issues](https://docs.microsoft.com/powershell/scripting/whats-new/known-issues-ps6).
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Steps to reproduce
|
||||
description: >
|
||||
List of steps, sample code, failing test or link to a project that reproduces the behavior.
|
||||
Make sure you place a stack trace inside a code (```) block to avoid linking unrelated issues.
|
||||
placeholder: >
|
||||
I am experiencing a problem with X.
|
||||
I think Y should be happening but Z is actually happening.
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Expected behavior
|
||||
render: console
|
||||
placeholder: |
|
||||
PS> 2 + 2
|
||||
4
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Actual behavior
|
||||
render: console
|
||||
placeholder: |
|
||||
PS> 2 + 2
|
||||
5
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Environment data
|
||||
description: Paste verbatim output from `$PSVersionTable` below.
|
||||
render: powershell
|
||||
placeholder: PS> $PSVersionTable
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Visuals
|
||||
description: >
|
||||
Please upload images or animations that can be used to reproduce issues in the area below.
|
||||
Try the [Steps Recorder](https://support.microsoft.com/en-us/windows/record-steps-to-reproduce-a-problem-46582a9b-620f-2e36-00c9-04e25d784e47)
|
||||
on Windows or [Screenshot](https://support.apple.com/en-us/HT208721) on macOS.
|
||||
39
.github/ISSUE_TEMPLATE/Distribution_Request.md
vendored
39
.github/ISSUE_TEMPLATE/Distribution_Request.md
vendored
|
|
@ -1,39 +0,0 @@
|
|||
---
|
||||
name: Distribution Support Request
|
||||
about: Requests support for a new distribution
|
||||
title: "Distribution Support Request"
|
||||
labels: Distribution-Request, Needs-Triage
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Details of the Distribution
|
||||
|
||||
- Name of the Distribution:
|
||||
- Version of the Distribution:
|
||||
- Package Types
|
||||
- [ ] Deb
|
||||
- [ ] RPM
|
||||
- [ ] Tar.gz
|
||||
- Snap - Please file issue in https://github.com/powershell/powershell-snap. This issues type is unrelated to snap packages with a distribution neutral.
|
||||
- Processor Architecture (One per request):
|
||||
- The following is a requirement for supporting a distribution **without exception.**
|
||||
- [ ] The version and architecture of the Distribution is [supported by .NET Core](https://github.com/dotnet/core/blob/master/release-notes/5.0/5.0-supported-os.md#linux).
|
||||
- The following are requirements for supporting a distribution.
|
||||
Please write a justification for any exception where these criteria are not met and
|
||||
the PowerShell committee will review the request.
|
||||
- [ ] The version of the Distribution is supported for at least one year.
|
||||
- [ ] The version of the Distribution is not an [interim release](https://ubuntu.com/about/release-cycle) or equivalent.
|
||||
|
||||
## Progress
|
||||
|
||||
- [ ] An issues has been filed to create a Docker image in https://github.com/powershell/powershell-docker
|
||||
|
||||
### For PowerShell Team **ONLY**
|
||||
|
||||
- [ ] Docker image created
|
||||
- [ ] Docker image published
|
||||
- [ ] Distribution tested
|
||||
- [ ] Update `packages.microsoft.com` deployment
|
||||
- [ ] [Lifecycle](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/docs-conceptual/PowerShell-Support-Lifecycle.md) updated
|
||||
- [ ] Documentation Updated
|
||||
64
.github/ISSUE_TEMPLATE/Distribution_Request.yaml
vendored
Normal file
64
.github/ISSUE_TEMPLATE/Distribution_Request.yaml
vendored
Normal file
|
|
@ -0,0 +1,64 @@
|
|||
name: Distribution Support Request
|
||||
description: Requests support for a new distribution
|
||||
title: Distribution Support Request
|
||||
labels: [Distribution-Request, Needs-Triage]
|
||||
body:
|
||||
- type: input
|
||||
attributes:
|
||||
label: Name of the Distribution
|
||||
validations:
|
||||
required: true
|
||||
- type: input
|
||||
attributes:
|
||||
label: Version of the Distribution
|
||||
validations:
|
||||
required: true
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Package Types
|
||||
options:
|
||||
- label: Deb
|
||||
- label: RPM
|
||||
- label: Tar.gz
|
||||
- label: Snap - Stop! Please file your issue in [PowerShell-Snap](https://github.com/powershell/powershell-snap) instead.
|
||||
- type: input
|
||||
attributes:
|
||||
label: Processor Architecture
|
||||
description: One per request!
|
||||
validations:
|
||||
required: true
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: .NET Core Support
|
||||
description: The following is a requirement for supporting a distribution **without exception.**
|
||||
options:
|
||||
- label: The version and architecture of the Distribution is [supported by .NET Core](https://github.com/dotnet/core/blob/master/release-notes/5.0/5.0-supported-os.md#linux).
|
||||
required: true
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Distribution Requirements
|
||||
description: The following are requirements for supporting a distribution.
|
||||
options:
|
||||
- label: The version of the Distribution is supported for at least one year.
|
||||
- label: The version of the Distribution is not an [interim release](https://ubuntu.com/about/release-cycle) or equivalent.
|
||||
- type: input
|
||||
attributes:
|
||||
label: Exemption Justification
|
||||
description: |
|
||||
Please write a justification for any exception where the above criteria
|
||||
are not met. The PowerShell committee will review the request.
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: Progress
|
||||
options:
|
||||
- label: An issue has been filed to create a Docker image in [PowerShell-Docker](https://github.com/powershell/powershell-docker)
|
||||
- type: checkboxes
|
||||
attributes:
|
||||
label: For PowerShell Team **ONLY**
|
||||
options:
|
||||
- label: Docker image created
|
||||
- label: Docker image published
|
||||
- label: Distribution tested
|
||||
- label: Update `packages.microsoft.com` deployment
|
||||
- label: "[Lifecycle](https://github.com/MicrosoftDocs/PowerShell-Docs/blob/staging/reference/docs-conceptual/PowerShell-Support-Lifecycle.md) updated"
|
||||
- label: Documentation Updated
|
||||
23
.github/ISSUE_TEMPLATE/Feature_Request.md
vendored
23
.github/ISSUE_TEMPLATE/Feature_Request.md
vendored
|
|
@ -1,23 +0,0 @@
|
|||
---
|
||||
name: Feature Request/Idea 🚀
|
||||
about: Suggest a new feature or improvement (this does not mean you have to implement it)
|
||||
title: "Feature Request"
|
||||
labels: Issue-Enhancement, Needs-Triage
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
## Summary of the new feature/enhancement
|
||||
|
||||
<!--
|
||||
A clear and concise description of what the problem is that the new feature would solve.
|
||||
Try formulating it in user story style (if applicable):
|
||||
'As a user I want X so that Y.' with X being the being the action and Y being the value of the action.
|
||||
-->
|
||||
|
||||
## Proposed technical implementation details (optional)
|
||||
|
||||
<!--
|
||||
A clear and concise description of what you want to happen.
|
||||
Consider providing an example PowerShell experience with expected result.
|
||||
-->
|
||||
20
.github/ISSUE_TEMPLATE/Feature_Request.yaml
vendored
Normal file
20
.github/ISSUE_TEMPLATE/Feature_Request.yaml
vendored
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
name: Feature Request / Idea 🚀
|
||||
description: Suggest a new feature or improvement (this does not mean you have to implement it)
|
||||
labels: [Issue-Enhancement, Needs-Triage]
|
||||
body:
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Summary of the new feature / enhancement
|
||||
description: >
|
||||
A clear and concise description of what the problem is that the
|
||||
new feature would solve. Try formulating it in user story style
|
||||
(if applicable).
|
||||
placeholder: "'As a user I want X so that Y...' with X being the being the action and Y being the value of the action."
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Proposed technical implementation details (optional)
|
||||
placeholder: >
|
||||
A clear and concise description of what you want to happen.
|
||||
Consider providing an example PowerShell experience with expected result.
|
||||
43
.github/ISSUE_TEMPLATE/Release_Process.md
vendored
43
.github/ISSUE_TEMPLATE/Release_Process.md
vendored
|
|
@ -1,43 +0,0 @@
|
|||
---
|
||||
name: Release Process
|
||||
about: Maintainers Only - Release Process
|
||||
title: "Release Process for v6.x.x"
|
||||
labels: Issue-Meta, Needs-Triage
|
||||
assignees: ''
|
||||
|
||||
---
|
||||
|
||||
<!--
|
||||
This template is for maintainers to create an issues to track the release process.
|
||||
Please **only** use this template if you are a maintainer.
|
||||
-->
|
||||
|
||||
## Checklist
|
||||
|
||||
- [ ] Verify that `PowerShell-Native` has been updated/released as needed.
|
||||
- [ ] Check for `PowerShellGet` and `PackageManagement` release plans.
|
||||
- [ ] Start process to sync Azure DevOps artifacts feed such as modules and NuGet packages.
|
||||
- [ ] Create a private branch named `release/v6.x.x` in Azure DevOps repository.
|
||||
All release related changes should happen in this branch.
|
||||
- [ ] Prepare packages
|
||||
- [ ] Kick off coordinated build.
|
||||
- [ ] Kick off Release pipeline.
|
||||
- *These tasks are orchestrated by the release pipeline, but here as status to the community.*
|
||||
- [ ] Prepare packages
|
||||
- [ ] Sign the RPM package.
|
||||
- [ ] Install and verify the packages.
|
||||
- [ ] Trigger the docker staging builds (signing must be done).
|
||||
- [ ] Create the release tag and push the tag to `PowerShell/PowerShell` repository.
|
||||
- [ ] Run tests on all supported Linux distributions and publish results.
|
||||
- [ ] Update documentation, and scripts.
|
||||
- [ ] Update [CHANGELOG.md](../../CHANGELOG.md) with the finalized change log draft.
|
||||
- [ ] Stage a PR to master to update other documents and
|
||||
scripts to use the new package names, links, and `metadata.json`.
|
||||
- [ ] For preview releases,
|
||||
merge the release branch to GitHub `master` with a merge commit.
|
||||
- [ ] For non-preview releases,
|
||||
make sure all changes are either already in master or have a PR open.
|
||||
- [ ] Delete the release branch.
|
||||
- [ ] Trigger the Docker image release.
|
||||
- [ ] Retain builds.
|
||||
- [ ] Update https://github.com/dotnet/dotnet-docker/tree/master/3.0/sdk with new version and SHA hashes for global tool.
|
||||
41
.github/ISSUE_TEMPLATE/Release_Process.yaml
vendored
Normal file
41
.github/ISSUE_TEMPLATE/Release_Process.yaml
vendored
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
name: Release Process
|
||||
description: Maintainers Only - Release Process
|
||||
title: "Release Process for v7.x.x"
|
||||
labels: [Issue-Meta, Needs-Triage]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: >
|
||||
This template is for maintainers to create an issues to track the release process.
|
||||
Please **only** use this template if you are a maintainer.
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: Checklist
|
||||
value: |
|
||||
- [ ] Verify that [`PowerShell-Native`](https://github.com/PowerShell/PowerShell-Native) has been updated / released as needed.
|
||||
- [ ] Check for `PowerShellGet` and `PackageManagement` release plans.
|
||||
- [ ] Start process to sync Azure DevOps artifacts feed such as modules and NuGet packages.
|
||||
- [ ] Create a private branch named `release/v6.x.x` in Azure DevOps repository.
|
||||
All release related changes should happen in this branch.
|
||||
- [ ] Prepare packages
|
||||
- [ ] Kick off coordinated build.
|
||||
- [ ] Kick off Release pipeline.
|
||||
- *These tasks are orchestrated by the release pipeline, but here as status to the community.*
|
||||
- [ ] Prepare packages
|
||||
- [ ] Sign the RPM package.
|
||||
- [ ] Install and verify the packages.
|
||||
- [ ] Trigger the docker staging builds (signing must be done).
|
||||
- [ ] Create the release tag and push the tag to `PowerShell/PowerShell` repository.
|
||||
- [ ] Run tests on all supported Linux distributions and publish results.
|
||||
- [ ] Update documentation, and scripts.
|
||||
- [ ] Update [CHANGELOG.md](../../CHANGELOG.md) with the finalized change log draft.
|
||||
- [ ] Stage a PR to master to update other documents and
|
||||
scripts to use the new package names, links, and `metadata.json`.
|
||||
- [ ] For preview releases,
|
||||
merge the release branch to GitHub `master` with a merge commit.
|
||||
- [ ] For non-preview releases,
|
||||
make sure all changes are either already in master or have a PR open.
|
||||
- [ ] Delete the release branch.
|
||||
- [ ] Trigger the Docker image release.
|
||||
- [ ] Retain builds.
|
||||
- [ ] Update https://github.com/dotnet/dotnet-docker/tree/master/3.0/sdk with new version and SHA hashes for global tool. NOTE: this link is broken!
|
||||
Loading…
Reference in a new issue