You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
[meta] clean up and document labels in this issue tracker #1549
changed the title [-]clean up and document labels in this issue tracker[/-][+][meta] clean up and document labels in this issue tracker[/+]on Apr 23, 2019
@clarkbw Did you want to handle the internal/external consistency yourself (b/c AFAIK you're the only GitHub staff who's also a collaborator here)? Else, if you gave some guidelines/docs, I'd happily help w/ that.
To perhaps start this, I'd like to meekly quote myself:
my rule-of-thumb is try to use label combinations that best express what the issue's about
somewhat independent of what else might be labeled such. Most of the time, related issues do end up grouped, but, sometimes, issues only conceptually similar do end up w/ the same label. #1547 (comment) makes a great example of this.
I think in a typical repo, this would be acceptable, & projects would be used to group more tightly-related issues, milestones grouping projects, &c. Here, how do we want to do it?
Does anyone mind if I emojify a few more labels, since @clarkbw has now set a (perhaps dangerous 😉) precedent w/ the update to the bug 🐛 label? Or should that be kept special?
Reacted by Adam Spiers and Ciro Santilli (三西猴) OurBigBook.com sponsor me: cirosantilli.com/sponsor, opinions my own 2020冠状病毒审查 ，2020郝海东 ，2018新疆改造中心，1989六四事件，1999法轮功 ，2019 996.ICU, 2018包子露宪，2015 709大抓捕，2015巴拿马文件 邓家贵，2017低端人口，2008西藏骚乱<script>alert(1)</script>
1 concern: existing manual links to these break whenever renaming labels (which includes adding emoji, naturally — it's why I edited a couple of our posts above). The UI links by GitHub rendering update fine, though. Is that important enough to keep from messing too much w/ these on a wholesale basis?
AFAIK, GitLab's ~<label> syntax solves this pretty neatly.
Thanks everyone for your contributions here! Can I suggest that we move this list of labels into a new file in the repo (e.g. LABELS.md or something like that)? That way anyone can submit PRs making the list better, and also it makes it more visible to end users.
Dunno if this rates a separated Meta issue: Would GitHub Actions be helpful in automatically applying these? That Labeler template seems mighty inviting.… except it's for PRs.…
Activity
[-]clean up and document labels in this issue tracker[/-][+][meta] clean up and document labels in this issue tracker[/+]TPS commentedon Apr 28, 2019
@clarkbw Did you want to handle the internal/external consistency yourself (b/c AFAIK you're the only GitHub staff who's also a collaborator here)? Else, if you gave some guidelines/docs, I'd happily help w/ that.
TPS commentedon May 5, 2019
To perhaps start this, I'd like to meekly quote myself:
somewhat independent of what else might be labeled such. Most of the time, related issues do end up grouped, but, sometimes, issues only conceptually similar do end up w/ the same label. #1547 (comment) makes a great example of this.
I think in a typical repo, this would be acceptable, & projects would be used to group more tightly-related issues, milestones grouping projects, &c. Here, how do we want to do it?
clarkbw commentedon May 9, 2019
I've made some progress so far on a first pass, will keep updating this as I go.
TPS commentedon May 17, 2019
Does anyone mind if I emojify a few more labels, since @clarkbw has now set a (perhaps dangerous 😉) precedent w/ the update to the bug 🐛 label? Or should that be kept special?
clarkbw commentedon May 17, 2019
TPS commentedon May 17, 2019
1 concern: existing manual links to these break whenever renaming labels (which includes adding emoji, naturally — it's why I edited a couple of our posts above). The UI links by GitHub rendering update fine, though. Is that important enough to keep from messing too much w/ these on a wholesale basis?
AFAIK, GitLab's
~<label>syntax solves this pretty neatly.captn3m0 commentedon May 23, 2019
-1 for Emojis in labels: #1580
TPS commentedon May 24, 2019
@cirosantilli Well, since I invited comment here, why's the separate issue needed? But you do make a good point. 🙇🏾♂️
cirosantilli commentedon May 24, 2019
I removed the bug emoji now since people seem to agree #1580
aspiers commentedon Jul 18, 2019
Thanks everyone for your contributions here! Can I suggest that we move this list of labels into a new file in the repo (e.g. LABELS.md or something like that)? That way anyone can submit PRs making the list better, and also it makes it more visible to end users.
TPS commentedon Aug 14, 2019
Dunno if this rates a separated Meta issue: Would GitHub Actions be helpful in automatically applying these? Thatexcept it's for PRs.…Labelertemplate seems mighty inviting.…TPS commentedon Sep 2, 2019
There's now the Issue Label Bot.… Whaddy'all think re: letting it loose here⁈
TPS commentedon Dec 21, 2019
The equivalent GitHub Action as
Labeler, but for issues, seems to betag-ur-it. (FWIW, it's been further developed by a GitHub ex-staffer.)