Continuing the discussion from Github boxes should be truncated:
If there was a way to avoid content truncation on a per-link basis we could be posting links to our GitHub-specific documentation and make it searchable here on Meta, e.g:
https://github.com/discourse/discourse/blob/master/docs/TROUBLESHOOTING.md
I’ve seen several examples of other open source forums that could benefit from this.
Why would we want this? The only way it would be searchable here is if it was duplicated, which isn’t particularly helpful.
I find the “helpful” feature of onebox expanding the first ~30 lines of a github readme file to be quite the opposite, 75% of the time… I can’t imagine why I would ever want it to expand to {infinity} lines.
It makes it so that our duplicate post checker can match users up with external docs such as this one.
For example the NPM community also has a use for this. They have a TROUBLESHOOTING.md file that would ideally show up in our similar posts search when users are writing support topics.
Unlimited is hugely risky, but maybe for a feature that adds a hint to truncate less … its is very hard to wrangle, only way I can think of is by abusing #
I’m not entirely clear how this is useful to anyone. The clickable link to the troubleshooting doc should appear, so there is one standard place for that information to be. Duplicating it in some weird onebox-y partial way is a net negative, duplicating it entirely is massively negative.
They could include a TL;DR summary at the top if they have an abbreviated version.
I took a look at https://github.com/npm/npm/blob/latest/TROUBLESHOOTING.md and it doesn’t look amenable to a 3-bullet-point version to me?