Add GitHub Action to pre-triage new issues

[Dongbo Wang (daxian-dbw)]

PR Summary

Add a GitHub Action to pre-triage new issue -- close the issues that are duplicate of #1306 and #1315

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure you've added one or more new tests
• Make sure you've tested these changes in terminals that PowerShell is commonly used in (i.e. conhost.exe, Windows Terminal, Visual Studio Code Integrated Terminal, etc.)
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed at PowerShell-Docs
    • Doc Issue filed:

Microsoft Reviewers: Open in CodeFlow

[Ilya (iSazonov)]

Bot war! 😄 Need to add auto issue creation in PSReadline 😄

[Ilya (iSazonov)]

Hmm, why not? If implement this reporting by telemetry users will do not create useless issues. Workflow would be: PSReadline error -> send a telemetry -> filter the telemetry -> create new issue only if needed.

[Dongbo Wang (daxian-dbw)]

Nice idea 👍 Most of the duplicate issues are reported against the old versions of PSReadLine, so the bot is still needed. As for your suggestion, the user interaction is still important because repro steps are important for us to really investigate the issue.

[Ilya (iSazonov)]

the user interaction is still important because repro steps are important for us to really investigate the issue.

I'd speculate 95% questions is about user environment. I believe it makes sense to enhance the trace error report with the information (terminal, its geometry, font, code page and so on).

As for user interaction, we could add a correlation id in the trace - if an user open new issue manually (copy-paste from screen or share screenshot) you could use the correlation id to search auto report in trace database.