-
Notifications
You must be signed in to change notification settings - Fork 216
optionally display label on issues #540
Comments
Hmm we actually have a flag for that already but it doesn't seem to be working. Currently I am working on completely refactoring the code base to use GitHub's GraphQL api. I will make sure this works when we release v2. At my current pace, I am estimating v2 will be release in April 2019. If that is too long for you to wait, I would be happy to merge a PR from you if you can find a fix for this. |
@protoEvangelion trying to get started on this, and did the steps outlined in Contributing, including |
@zevaverbach no problem at all! I am happy to help 😄 Try this:
Let me know if that works. If not please let me know which file you are trying to log from. |
@protoEvangelion awesome, thanks! See #550. |
On second thought I think I misread your intent. |
@protoEvangelion after having delved into the codebase a little, I realized that what I really wanted was for labels to be displaying when the So no, I didn't have that particular use case in mind, but that's good to know about #550 accomplishes what you suggested above, only using |
Thanks for the clarification. I think it would be ideal to only show labels in |
…nonexistent attribute `issue.label`, fixed with `issue.labels`. Further down, the `labels` array was pushed to from itself with `label.name`, rather than making a fresh array of label strings for display. Finally, made a distinctive color for issue display and displayed the appropriate singular/plural of 'label'.
perhaps with
--label
?The text was updated successfully, but these errors were encountered: