-
Notifications
You must be signed in to change notification settings - Fork 60k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jekyll GFM processor claims it "will always match the results you see on GitHub" #34334
Comments
@janbrasna Thanks so much for opening an issue! I'll get this triaged for review ✨ |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
@janbrasna Thank you for your patience while our team reviewed! They are in agreement with you that the wording should changed to reflect reality 💛 I've added the |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
What part(s) of the article would you like to see updated?
Originally posted by @rectalogic in actions/jekyll-build-pages#106
That is not true, GFM hasn't added the newer dotcom features as callouts, diagrams, ToC etc. so this sounds too bold given the discrepancies.
Additional information
Additional info #32988 (comment) and below wrt differences in products +link to Jekyll-only specific issue in the past.
The text was updated successfully, but these errors were encountered: