DenverCoder1/readme-typing-svg

[DOCS] Use issue forms instead of issue templates

Chiusa

#229 aperta il 18 lug 2023

Vedi su GitHubGuida contributor
 (2 commenti) (0 reazioni) (0 assegnatari)PHP (606 fork)batch import
choregood first issue

Metriche repository

Star
 (3984 stelle)
Metriche merge PR
 (Nessuna PR mergiata in 30 g)

Descrizione

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.

Guida contributor

Direzione di ricerca
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
Nessuno
Dominio
documentationdeveloper experience
Tipo issue
Funzionalità
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 ore
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Datata
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Chiara
Prerequisiti
basic YAML syntaxGitHub issue templates
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
70