DenverCoder1/readme-typing-svg

[DOCS] Use issue forms instead of issue templates

Closed

#229 opened on Jul 18, 2023

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)PHP (606 forks)batch import
choregood first issue

Repository metrics

Stars
 (3,984 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe.

We can convert the current issue templates to issue forms, which have more variety of options and also have required fields, dropdowns, and so much more.

Describe the solution you'd like

Convert the issue templates to issue forms.

Describe alternatives you've considered

Keep the current templates, but improve them.

Additional context

None.

Contributor guide

Research direction
The issue involves converting existing issue templates in the .github/ISSUE TEMPLATE directory to YAML based issue forms. Refer to GitHub's documentation on issue forms. The existing templates are Markdown files; they need to be converted to YAML with fields like type, dropdowns, and required fields. No linked PRs or additional comments provide specifics, so start by examining the current template files.
Tech stack
None
Domain
documentationdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
basic YAML syntaxGitHub issue templates
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70