Web clipper · Local

How to clip a GitHub issue to PDF without the whole repository chrome

Clip a GitHub issue to PDF by selecting the visible report and comments you need. Excerpt is a local page selection, not an official GitHub exporter.

Also on Microsoft Edge Add-ons

An issue thread is often more useful than the surrounding repo chrome, and it can be hard to find again after the tab closes. If you clip a GitHub issue to PDF (or Markdown), open the issue, expand the comments you need, and select those blocks—not the whole repository, and not a promise that Excerpt is an official GitHub exporter.

This is distinct from clipping a README or an API docs page, and distinct from a Claude code-review workflow. The path is the web clipper in Chrome or Edge. It will not pull comments you never loaded, will not bypass a private-repo login, and will not post a reply.

Clip a GitHub issue to PDF in four steps

  1. Open the issue URL and wait until the body and the comments you care about are rendered. Expand hidden or outdated comments only if you need them, so they become selectable text.
  2. Select the title, labels if they are visible and useful, the original report, and the comments you will keep. Skip the repo header, file trees, and “similar issues” rails.
  3. Export Markdown if you will turn a comment into a ticket or a patch note, and PDF if you need a frozen snapshot. Add the issue number, repo, and date in a header or tag.
  4. Check that code blocks and error logs still read cleanly. If a later comment is missing, it was probably still collapsed or below an unloaded page.

Honest limits

  • Private issues you cannot open cannot be clipped. Do not treat the extension as an access bypass.
  • Edits, deletions, and later comments will not update a PDF you already saved.
  • This is not a GitHub backup of every issue in the repo, and it is not a substitute for official enterprise export or legal hold.

If the useful object is a pull request rather than an issue, open that PR and clip the visible discussion or files the same way, clearly labeled, rather than mixing two kinds of thread into one unlabeled file.

Secrets, logs, and attribution

Redact tokens, customer data, and internal hostnames before you save, even if they were already in the issue. Keep usernames with the comments you might cite. Official work still happens on GitHub; the local clip is a working extract you can search next to other notes. Free includes 100 clippings and 5 tags; Pro is $29 one-time for unlimited clippings plus backup import/export. There is no cloud sync and no AI issue summarizer claimed as shipped.

File the issue you will actually reopen

Use Chrome or Edge, expand the comments first, and treat the PDF as a dated excerpt of a visible thread—not as a complete GitHub archive of the repository.

FAQ

Is Excerpt an official GitHub issue exporter?

No. It clips the visible issue body and comments you select and saves PDF or Markdown locally.

Will collapsed or unloaded comments appear in the PDF?

Only if you expand them so the text is on the page and include them in the selection.

Install Excerpt and save your next clip as a clean PDF

Free: up to 100 clippings and 5 tags. Pro is $29 one-time for unlimited + library backup import/export.