Encoding/formating problems in migrated GitHub issues

I got the invitaion to join the "LLVM" organization on GitHub today
and I was a bit puzzled why - but then I remembered the bugzilla
migration is coming up. I was just aware of this since I follow the
repo and LLVM Weekly a bit - others might not be aware what this is
actually a bit. Fortunately my mail adresses matched so I could be
migrated - wasn't aware of a form to register... but I digress.

I took a look at my issues in GitHub and I came across some with
enconding/formating issues:

In the title some HTML encoded character was introduced changing a
simple "@private" from the original report to "@​private".

Since GitHub uses Markdown by default the "__VA_ARGS__" in the sample
code is now bold and the code is no longer valid.

The sample code in this is all messed up since it is treated as
Markdown. This seems to be true for several of my reported issues.

It is probably extremely late to the report this if this is supposed
to go live by tomorrow but the Markdown issues appears to be pretty
bad to me since you will not be able to get the actual source code if
you are not allowed to edit the post.

Hello

Thank you for your comments.

First of all, our bugzilla contains 17k+ open issues. We will
certainly make them writeable after the conversion.

-Wdocumentation-unknown-command does not recognize @​private · Issue #37161 · llvm/llvm-project · GitHub
In the title some HTML encoded character was introduced changing a
simple "@private" from the original report to "@​private".

As you can imagine, LLVM IR contains lots of things like "@foo", "#1"
and "!123". All these create references to other github objects –
issues or (even worse) github users. There is no way we can "escape"
such sequences. The only viable solution is to insert a zero-width
space symbol between e.g. "#" and number. However, it turns out that
GitHub markdown engine renders such things differently – it ignores
such symbols in e.g. titles (however, will happily notify github user
@private in such case).

We tried to limit the amount of sanitizing rewriting we're doing. But
still there will be false positives and negatives.

cannot suppress modernize-avoid-c-arrays in macros · Issue #46511 · llvm/llvm-project · GitHub
Since GitHub uses Markdown by default the "__VA_ARGS__" in the sample
code is now bold and the code is no longer valid.

This is expected, yes, as GitHub is all markdown and there is no way
one could disable the markup. Copying everything into a code block is
not an option as well, as it does not scroll and word-wrap properly,
etc.

clang-analyzer-cplusplus.NewDeleteLeaks false positive · Issue #47628 · llvm/llvm-project · GitHub
The sample code in this is all messed up since it is treated as
Markdown. This seems to be true for several of my reported issues.

See above.

First of all, our bugzilla contains 17k+ open issues. We will
certainly make them writeable after the conversion.

But the posts might only be writable fro the actual poster and not
the ones replaying/working on them.

Somethind I forgot to consider is that the original issues are still
linked so you can go back to them for the actual code. Jumping being
between bugzilla and GitHub to follow the correct code snippets will
be annoying though.

If the tickets are editable though they could be changed to use code
blocks were appropriate.

This is expected, yes, as GitHub is all markdown and there is no way
one could disable the markup. Copying everything into a code block is
not an option as well, as it does not scroll and word-wrap properly,
etc.

Using a code block would certainly be the wrong approach.

Some of the code changes seemed awfully messy though so I think I
bring it up. Although the sneaky ones where the code might not look
like it was changed at all but things are actually omitted (like the
underscores in the macro in that one example) could cause some
issues.

Something else I just noticed is that the subscriptions for all my
reported issues are not enabled in GitHub. So I would have to enable
all of these manually to receive any updates. Seems to be the same
for ones where I just added myself to CC.