[Documentation] switch-to-issue-forms

[L483]

Object of Interest

The issue templates

Problem/Motivation

Issue forms enable a better presentation as well as better validation possibilities. They can also enforce using a template when creating a new issue. Also, the issue form configuration file is the single point of truth that contains all information concerning the issue form, like default labels, assignees, etc.

Solution Proposal

Convert every issue template to a GitHub issue form configuration file. Keep the old issue templates to allow for an individual choice between these two options.

The security issue template is excluded because it will be dropped in favor of GitHub's security advisories as mentioned in issue #20.

Impact

When updating a template, it will be necessary to change two files instead of one to keep the contents of the classic issue template and the new issue form synchronous.

Acceptance Criteria

• create bug report form
• create design form
• create documentation form
• create feature change form
• create feature drop form
• create feature request form
• create maintenance form
• create performance form
• create pipeline form
• create question form
• create refactor form
• create testing form
• create text correction form
• create tooling form

Further Information

• configuring issue templates for your repository
• creating issue forms
• syntax for GitHub's form schema
• syntax for issue forms
• Learn YAML in Y minutes

Related Issues

• [Feature Drop] remove-security-issue-template #20