Our customer has reported a peculiar issue with reporting commit statuses from TeamCity to GitHub: if he used an emoji Unicode symbols withing the TeamCity build configuration name (that translates into “context” field when the build status is published to GitHub), GitHub rejects such a request, returning HTTP error 422 Unprocessable Entity.
I recon GitHub doesn’t like emojis. We have tested it with a number of other character sets, such as Kanji, Cyrillic, Hebrew and Arabic scripts, even Indian rupee sign (the latter was introduced in Unicode 6.0 together with the first emojis), and GitHub accepts all of that.
Now the questions are:
- Is such an arrangement intentional?
- And if so, is there any specification of what constitutes an acceptable character set for the “context” field there?