ER: Generic good first issue template for developers
Offen
@JessicaLucindaCheng arbeitet bereits daran.
Seit 28.11.2023.
Complexity: Missing
Complexity: See issue making label
ER
Feature: Board/GitHub Maintenance
Issue Making: Level 2
role: back end/devOps
role: dev leads
role: front end
size: 1pt
status: Updated
- Vorherrschende Sprache
- JavaScript
- Sterne
- 364
- Forks
- 873
- Ø Merge
- 2 T. 23 Std.
- Gemergte PRs (30 T.)
- 18
Beschreibung
Emergent Requirement - Problem
- Since we write a lot of good first issues, it would be helpful to have a generic good first issue template for writing developer issues.
- This template would be used to write good first issues for
role: front endand/orrole: back end/devOps.
Issue you discovered this emergent requirement in
- #4362
Date discovered
2023-04-24 at Dev/PM meeting
Did you have to do something temporarily
- YES - I just write issues using the regular blank issue template
- NO
Who was involved
@JessicaLucindaCheng
@bonniewolfe
What happens if this is not addressed
We have to write good first issues using the blank issue template or blank issue form.
Resources
- Examples of good first issues:
- #4449
- #4491
- #4141
Recommended Action Items
- Make a new issue for a developer to work on creating a generic good first issue template
- The new issue should include the labels:
Issue Making: Level 2andComplexity: See issue making label.
- The new issue should include the labels:
- Discuss with Merge Team if you need help writing the issue or have questions
Potential solutions [draft]
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.