Export GitHub issues and pull requests to CSV, Excel, or JSON
A Chrome extension that adds an Export button to any GitHub issues or pull-requests list and downloads the whole list, every page, with every field. It runs in your browser using GitHub's official API. No account, no analytics.
Why this exists
GitHub has no built-in export for issues. The community request has been open since 2019. Most workarounds export only the first page, need an API script, or cap free exports per month.
What you get
- Every item matching the list's current filters: labels, milestone, assignee, state, and search text are all respected.
- All pages automatically. Lists with more than 1,000 items are split by creation date behind the scenes so nothing is skipped.
- Fields: number, type (issue or pull request), title, state, author, labels, assignees, milestone, comment count, created, updated, closed, merged, draft, URL, and optionally the description text.
- Formats: CSV (UTF-8 with byte-order mark, opens cleanly in Excel and Google Sheets), Excel
.xlsx, or JSON. - Spreadsheet formula injection is neutralised: cells starting with
=,+,-, or@are escaped.
How it works
| Without a token | Works on public repositories. GitHub allows 60 API requests per hour, which covers about 6,000 items per hour. |
|---|---|
| With a fine-grained token | Private repositories and 5,000 requests per hour. Create one at GitHub with only Issues: read-only and Pull requests: read-only. It is stored in Chrome's local extension storage on your device and sent only to api.github.com. |
| Permissions | storage for the optional token, host access to api.github.com, and a content script on GitHub issue and pull-request list pages. |
| Data | Nothing is collected. There are no servers and no telemetry. See the privacy notice. |
Frequently asked
Can it export pull requests?
Yes. Open the Pull requests tab, apply filters, click Export. Merged date and draft status are included.
Does it include comments?
It includes the comment count for each item. Exporting the comment text itself is planned; it multiplies API requests, so it will be opt-in.
Is it open source?
The source is in the extension package and will be published with the listing. There are no hidden network calls to find.