org-mode not rendering #209313
🏷️ Discussion TypeBug Bodyorg-mode rendering seems to be broken. https://github.com/github/markup/ has not been updated and still lists org-mode support, so I'm guessing it's not intentionally removed? Expected: rendered HTML output Tried with 3 different repos with org files and they do not render:
|
Replies: 19 comments 21 replies
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
I am also experiencing this issue. I hope the maintainers can investigate and fix it as soon as possible. |
|
Same. Please fix this. |
|
Confirm fixed. |
|
Also affected. |
|
Same here, all the I dug in a bit: it's only Org, and it's every Org file. Creole, Textile, RST, AsciiDoc and the rest still render fine. github/markup still supports Org, and it renders correctly when I run it locally, so this looks like something changed on GitHub's side rather than a deprecation. I opened an issue with the details: github/markup#2105 If you're affected too, upvoting this discussion should help it get noticed. |
|
I got a response from Cassidy, the Director of Developer Experience at GitHub. Hopefully, everything gets sorted out soon! 
|
|
same issue here |
|
Same issue, very unfortunate |
|
GitHub has normalized continuous regressions in production software in the past few years. |
|
It is part of the MS onboarding process. |
|
👋🏽 Been two days - any updates? |
|
Sorry, but I’m not going to switch to |
|
Have they said they won't fix it? |
|
@kd5050612-debug did you just post AI slop here? |
|
What, specifically are you asking me? Consult your LLM to refine your question into a coherent one. |
I don't think it's ok to call strangers bro. I don't even understand what you're trying to say. |
|
It's been 3 days.... What the.... |
|
@github Wake up! This is fucking ridiculous. At least have someone respond instead of https://github.com/nix-community/emacs-overlay |
|
It's hard to tell what's going on from outside. But it's clear that the human team is the blocker in getting this fixed. |
|
Same here. |
|
Might be moot to add just a “pain point”, but...I'm also being bitten by this issue. I have several repositories where many of my READMEs and documentation files are in org-mode where this format makes more sense. It's all broken now 🙁 |
|
Fixed now. |
|
It seems to me that it's fixed, the rendering is working again. Can someone confirm? |
|
Looks good on my side. |
|
Confirm on my repos - the render of Org files is working properly. |
|
Curious that no commits were made in https://github.com/github/markup so likely was an infrastructure/configuration issue. The github team should illuminate the situation and explain what happened and why it took so long to address. |
|
Solved for what I can see. |
|
Confirmed for me as well. Cheers! |
|
Hi there! I can confirm Org-mode should be working again. I don't have further details to share at this time, but please let us know if you continue to have issues. |
|
Will you have more details or are y'all gonna leave us hanging wondering if/when this is gonna repeat and with the same or worse multi-day pain? |
|
A bit of transparency would be nice. |
|
Update with more details: Org-mode is working again. Rendering was temporarily disabled while we addressed an issue in the components that process Org-mode content. Restoring it involved code changes, testing, and deployment, not just changing a setting. Those changes were made outside the public github/markup repository, so its commit history doesn’t reflect that work. The issue that prompted this interruption has been addressed on GitHub.com. |
|
Good information. Will the public code ever reflect the changes made? |
|
Confirmed. This appears to be a regression rather than an intentional removal of Org-mode support. GitHub's current documentation still lists Org as a supported rendered prose format, and the I'm seeing the same behavior across multiple repositories: instead of rendering the Org file as HTML, GitHub displays the Org-mode source directly. Since this affects unrelated repositories and existing Would be great if the GitHub team could confirm whether this is a known regression. |
|
So it's still happening? Seems to be working on my side. |
Update with more details: Org-mode is working again. Rendering was temporarily disabled while we addressed an issue in the components that process Org-mode content. Restoring it involved code changes, testing, and deployment, not just changing a setting. Those changes were made outside the public github/markup repository, so its commit history doesn’t reflect that work.
The issue that prompted this interruption has been addressed on GitHub.com.