PR Summary

This uses the new, modern, GitHub Issue Forms. Or at least, it will when the beta opens up wider!

Update: checkout the GitHub Issues Announcement!

PR Context

I enabled similar forms in vscode-powershell yesterday after being added to the closed beta, and they're great! These forms provide a richer and easier experience to contributors, resulting in more consistent and concise issues being opened.

Note that I used a branch in this repo and not a fork so that we will be able to preview the forms before merging, which requires viewing the file in a repo for which the feature is enabled. Can't do that yet because the beta needs to open so we can add PowerShell/PowerShell to it, and doing that with a fork is harder and unnecessary work. All public repos are now automatically in the open beta!

I am not sure if similar forms can be used for Pull Requests. I haven't seen it mentioned in the documentation, but it's a very new feature, it's probably coming!

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: