Originally created by @veggiemonk on GitHub (Jun 24, 2018).
Link reference used to be of the kind
```
[@spotify][spotify]
[sportify]: https://github.com/spotify
```
But now it is left unprocessed. 😞
Anybody has any idea how to deal with this ?
@agebhar1 commented on GitHub (Jun 24, 2018):
I can't find any indication for a change for markdown processing either on https://github.com/github/markup nor https://githubengineering.com/. Also the the GFM specs still contains [reference links](https://github.github.com/gfm/#full-reference-link). Hopefully it's temporarily.
It was my fault but Stacey from Github found the issue.
Hey Julien,
It looks like the following link on line 709 as parenthesis around the link which seems to be breaking the subsequent references:
[ContainX](https://github.com/ContainX)
Changing the syntax to [ContainX] : https://github.com/ContainX should fix it up!
Cheers
Stacey
@veggiemonk commented on GitHub (Jun 25, 2018):
It was my fault but Stacey from Github found the issue.
```
Hey Julien,
It looks like the following link on line 709 as parenthesis around the link which seems to be breaking the subsequent references:
[ContainX](https://github.com/ContainX)
Changing the syntax to [ContainX] : https://github.com/ContainX should fix it up!
Cheers
Stacey
```
Fixes in https://github.com/veggiemonk/awesome-docker/commit/3c57f60e1201192d15e20ed2a6f994c91d41e3c9
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @veggiemonk on GitHub (Jun 24, 2018).
Link reference used to be of the kind
But now it is left unprocessed. 😞
Anybody has any idea how to deal with this ?
@agebhar1 commented on GitHub (Jun 24, 2018):
I can't find any indication for a change for markdown processing either on https://github.com/github/markup nor https://githubengineering.com/. Also the the GFM specs still contains reference links. Hopefully it's temporarily.
@veggiemonk commented on GitHub (Jun 25, 2018):
It was my fault but Stacey from Github found the issue.
Fixes in https://github.com/veggiemonk/awesome-docker/commit/3c57f60e1201192d15e20ed2a6f994c91d41e3c9