Repository navigation
Reopen issue #904 #1036
Description
Please reopen issue #904. The fact that GitHub is transitioning to Common Mark in now way removes the 100s of people who upvoted having a TOC. Same issue, just implement it in Common Mark, or whatever markup language GH decides to do next.
Therefore, this comment does not justify closing the issue.
Again, we don't care what markup language, just please add a TOC.
So, the issue should still be open.
Activity
tukkek commentedon Mar 29, 2017
I agree with the sentiment here but I don't think opening a new issue is going to solve the problem or is the best way to handle this. In the end, this is GitHub's playground and we must play by their rules and take their decisions. We can keep posting on the closed issue as long as the discussion is pertinent but let's try not to open more issues as this pollutes the tracker and isn't helpful in reading the entire conversation either.
abalter commentedon Mar 29, 2017
@tukkek I'm saying reopen #904 which was closed. I'm posting an issue to do that.
GitHub is the one saying we should open a new issue. The result is that we lose all the provenance of the support of hundreds of individuals who have expressed their desire for the feature, not to mention the thoughtful and constructive remarks they have already made. Or, some diligent person could patiently copy them over to the Common Mark thread...
shawnajean commentedon Mar 30, 2017
Hi there! I understand your sentiment. And I will definitely add your +1 to our internal feature request regarding adding a TOC syntax to GitHub Flavored Markdown. The original issue was not closed because we disagree or don't understand your frustration. That issue was closed because leaving it open is honestly disingenuous to the community members participating there.
When we look for features to add to markdown, we will not be looking in this, the markup repo, for that information. We will be looking at the information collected by our support team. It doesn't do us or you any good to leave an issue open collecting +1s and thumbsups that we here at GitHub will never actually see or record in a timely or efficient way.
The way to file a feature request for markdown features on GitHub and have your suggestion count is through our support team:
https://github.com/contact
And since we're using CommonMark now, feel free to chime in on the CommonMark forums about getting this feature added directly to CommonMark rather than as a GitHub-specific extension.
abalter commentedon Mar 30, 2017
@shawnajean what can you and the other GitHub developers do to communicate to the hundreds of people who have already requested this feature in two different issues to
We can't tell if you want us to just leave you alone, or if GitHub is actually interested in implementing this extremely simple feature.
#1037
#904
tukkek commentedon Mar 30, 2017
I understand your point @shawnajean, but isn't that a weird way of handling your markup issues? Behind closed doors instead of using the official GitHub repository issue tracker for that?
I mean, what's so wrong with your own platform that you guys would rather not use it in favor of some internal process where your users can't follow or participate in? Didn't you guys create the GH issue tracker exactly to handle this type of thing? If it's lacking in some way, shouldn't it be fixed, instead of abandoned in favor of your own internal tools?
EDIT I mean, the issue tracker here is excellent, I can't see why you wouldn't use your own product for this?
jotumn commentedon Mar 31, 2017
I guess someone needs to implement a 1-click button to automate sending the "contact support" message with issue link and description for all official Github repos :) Because obviously only a very tiny minority will go through the hassle of using the contact form.