davidbgk
/
larlet-fr-david
Следить 1
В избранное 0
Форкнуть 0
Код Релизы 0 Активность
Repository with sources and generator of https://larlet.fr/david/ https://larlet.fr/david/
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
263 коммитов
1 ветка
Дерево: 02a2a92b21
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из '02a2a92b21'
${ noResults }
larlet-fr-david/david/stream/2018/04/26/index.md

index.md 1.1KB
Исходник Normal View История

Add initial content
4 лет назад
​
​
​
​
​
​
​
 12345678 
  1. title: Issues & labels

  2. lang: en

  3. 

  4. > The number and diversity of issues and pull requests that Maintainers receive can sometimes be overwhelming. Both Maintainers and contributors have said that better issue labeling would make it easier to maintain and contribute to lessons. Being able to categorize contributions would help Maintainers to think through the type of issues being reported, and allow them to identify suitable next steps to address them. Issue labels are also useful for facilitating communication among Maintainers.

  5. > 

  6. > <cite>*[Developing GitHub labels for The Carpentries lessons](https://software-carpentry.org/blog/2018/04/github-labels.html)* ([cache](/david/cache/44d3835f51fb30798e01393928cbc718/))</cite>

  7. 

  8. Interesting how they chose to split the labels across [status and types](https://docs.carpentries.org/topic_folders/maintainers/github_labels.html) ([cache](/david/cache/544479c8eb56a822775056c9d4e928b7/)), it is very close to the need we had recently to report both the progress of the work and the kind of task to perform. I am looking forward to try these out, do you have a constrained number of labels in your team?