Add Playground Tools issue templates

[flexseth]

What?

Adds issue template starting point for Playground Tools

Why?

Creates guidelines for better error reporting

How?

Creating an issue template

Testing Instructions

1. Allow issue templates on the
   Playground Tools repo
2. Check or merge PR
3. Open a new issue and use the Playground Tools issues - wp-now, VS Code extension, utilities template
4. See if it suits the needs or needs updating

[flexseth]

@adamziel - if you can please review this PR to add an issues template for error reporting, it may be improved when more of the known issues docs come online.

For now, it can set the stage for some info we'd like to collect when reporting errors.

It's a little less detailed than the Playground online issue template, because the end users is assumed to be a little more advanced.

[flexseth]

Please take a look at this and let me know what you think, @adamziel

[flexseth]

changes made per request

[ironnysh]

Suggestion: add a GitHub workflow to auto-label issues when submitting (see example on WordPress Learn)

[adamziel]

Shouldn't this be a .yml file living in .github/ISSUE_TEMPLATE? Or will it work as a .md file living in .github?

[flexseth]

It depends how it was created, I'll have to go back through the workflow to figure out how it should be named

[flexseth]

Shouldn't this be a .yml file living in .github/ISSUE_TEMPLATE? Or will it work as a .md file living in .github?

TLDR; It'll work as submitted :)

---

The way I created it (screen flow attached) - used the Markdown issue syntax.

issue.templates.flow.mov

---

Looks like it can be either. 

Advanced issue templates

For more advanced issue flows, utilizing GitHub Actions etc - you can provide additional metadata via YAML. This can help with automatically labeling or assigning issues, and allows additional markup options (more similar to HTML input)

YAML syntax for issue templates

Advancing the PR

Want to start with Markdown and see if the YAML implementation provides more value, via automation, in the future?

[flexseth]

Suggestion: add a GitHub workflow to auto-label issues when submitting (see example on WordPress Learn)

Awaiting feedback about implementing automated workflows, or starting out with a basic issue template

Here's the PR though!

[flexseth]

@adamziel - this should be it!!

[flexseth]

Shouldn't this be a .yml file living in .github/ISSUE_TEMPLATE? Or will it work as a .md file living in .github?

It's throwing a warning on the Playground Tools (this) issue template.

---

Screenshot

---

Strangely, I don't see the same notice on the primary Playground repo issues template

Want me to figure it out?