Issue Cards Not Rendering Emojis nor MD Formatting #23393
-
While using GH Community I noticed that the Issue cards generated from links to Issues on GitHub.com repositories are not rendering emoji inside labels:
CONTRIBUTING.md : Git(hub) mini guide don't works
### Description of the Issue The steps to setup the fork for contribution don'…t works with a new fork and git up to date. Steps to Reproduce the Issue
Expected BehaviorShould works. Actual Behavior 1The second command generate the error: Fix 1Run: Actual Behavior 2After use the fix 1 the second command generate another error: Fix 2On the second command replace the More infoI let more experienced users check if theses fix are good or tricky. And I let english native speaker update the CONTRIBUTING.md file. As you can see in the above card, the emoji in the labels are rendered as text. Also, markdown formatting is not rendered either. I’m not sure how and where these cards are generated (i.e. whether they are generated by GitHub or a third party service) and I know that since they are intended for any type of external link they don’t necessarily abide to GitHub convention. But, in case they are being generated by GitHub, it would make sense that their generator would be context aware regarding URLs pertaining to GitHub Issues, PRs, Discussions, etc., and render labels, emoji and markdown formatting accordingly. You might wonder why I prefix every label with an emoji icon. The answer is that they allow grouping related labels by topic, using a common emoji (e.g. a 💀 for problematic issues, and 🔨 for tools, a 📚 for documentation, etc.). Since emojis are indexed as text, they are sorted Asciibetically, which ultimately allows labels to be listed as if they were in groups. Also, emoji icons allow to quickly spot labels by type, without necessary having to read them. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Hey there, welcome back to the GitHub Support Community! I’m fairly certain these cards may be generated by Discourse (the third-party service that GitHub uses for this forum) with some help of custom GitHub configuration in the backend. I do agree that emojis and Markdown should be rendered in these cards when referred to in forum threads. I would typically refer you to the official feedback form on GitHub, but that only refers to GitHub services and not the support community forum. We appreciate the feedback and I’ll relay this thread to staff! Thank you 😁 |
Beta Was this translation helpful? Give feedback.
-
Hi @tajmone and @Gisgar3 I thank you both some much for surfacing and discussing this pattern! We’ll take a look into it. |
Beta Was this translation helpful? Give feedback.
-
Hi @tajmone New posts with purebasic emojis render successfully now from my view. We checked in with our platform support and they’ve pushed some new changes regarding this. Would be able to tell me if you see the same result?
CONTRIBUTING.md : Git(hub) mini guide don't works
### Description of the Issue The steps to setup the fork for contribution don'…t works with a new fork and git up to date. Steps to Reproduce the Issue
Expected BehaviorShould works. Actual Behavior 1The second command generate the error: Fix 1Run: Actual Behavior 2After use the fix 1 the second command generate another error: Fix 2On the second command replace the More infoI let more experienced users check if theses fix are good or tricky. And I let english native speaker update the CONTRIBUTING.md file. |
Beta Was this translation helpful? Give feedback.
-
nyahbhinghiprincess:
I confirm, I can see the emojis correctly in you new card (also tested with in preview) and it works! That was great, thanks for the improvement. |
Beta Was this translation helpful? Give feedback.
Hey there, welcome back to the GitHub Support Community! I’m fairly certain these cards may be generated by Discourse (the third-party service that GitHub uses for this forum) with some help of custom GitHub configuration in the backend. I do agree that emojis and Markdown should be rendered in these cards when referred to in forum threads.
I would typically refer you to the official feedback form on GitHub, but that only refers to GitHub services and not the support community forum. We appreciate the feedback and I’ll relay this thread to staff! Thank you 😁