microsoft/PowerShellForGitHub

Remaining work for API Completeness

Aperta

#70 aperta il 11 dic 2018

Vedi su GitHubGuida contributor
 (12 commenti) (0 reazioni) (0 assegnatari)PowerShell (189 fork)auto 404
api completenessenhancementgood first issuehelp wanted

Metriche repository

Star
 (635 stelle)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

Guida contributor

Direzione di ricerca
Scegli una voce non spuntata dall'elenco, crea una nuova issue per tracciarla, implementa l'endpoint API GitHub corrispondente in PowerShell e invia una pull request.
Tech stack
shell
Dominio
apibackend
Tipo issue
Funzionalità
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
Oltre 1 settimana
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Attiva
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Chiara
Prerequisiti
PowerShellGitGitHub API basics
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
70