Repository navigation
GitHub issue not processed properly with readability #972
Description
Example page: bluedotimpact/bluedot#965
Expected: The title, comments and key metadata e.g. labels are extracted
Actual: only the first comment contents is extracted. This misses the issue title, labels, activity or further comments.
Example page output
<div id="readability-page-1" class="page">
<div data-testid="markdown-body" data-team-hovercards-enabled="true" data-turbolinks="false" id="issue-body-viewer">
<p dir="auto"> The old course hub is hosted at: </p>
<p dir="auto">
<a href="/api/browser/proxy?url=https%3A%2F%2Fcourse.bluedot.org%2F" rel="nofollow">https://course.bluedot.org/</a>
</p>
<p dir="auto"> We should set up redirects with nginx that direct people to all the right places (e.g. <code>https://course.bluedot.org/home/alignment</code> -> <code>https://bluedot.org/courses/alignment</code>, and others) </p>
</div>
</div>
Activity
LAST7 commentedon Jun 28, 2026
Hi there, I'm trying to utilize Readability on Github issues pages(and many other pages) as well and encounter the same problem as you've described. May I ask have you found a workaround? Maybe another library for extracting web page content?