It's announced here as also being in beta for public repos: https://github.blog/changelog/2021-06-23-issues-forms-beta-f...

I cannot comprehend why GitHub chose to let people define the form elements in YAML (!) instead of simply allowing <input>, <select> and <textarea> in Markdown. One of the most beautiful aspects of Markdown is that it supports HTML. It's trivial to allow only a minimal set of attributes, like `required`.

I kind of hate this to be honest. I understand why maintainers use them, because "i am having issues running it, plz halp", but IMHO two paragraphs of a well-written report which contains all the information is better than:

== Describe the problem (huge header) ==

Description of the the problem.

== What did you expect? ==

That it worked

== What did you get? ==

A repeat of the problem statement.

== Which version did you use? ==

Repeat of what I wrote in the description where I mentioned I tried latest release 1.2.3 and the latest master.

etc.

I generally delete these templates, making sure the requested information is all in there of course. It almost always saves significant amount of space and makes things easier to read. I haven't had any complaints thus far.

Shipped today. https://github.blog/changelog/2021-06-23-issues-forms-beta-f...

> Dive into work faster with issue forms and templates

Looks like its the same alpha/beta.

Thanks. I missed that list item, because it did not have a corresponding screenshot / screencast.