Export GitHub issues to CSV for free.
Turn a selected GitHub issue list into CSV with issue numbers, titles, labels and links.
Start with a filtered GitHub Issues page with a readable selection of issue rows.
Chrome extension + account required.
25 free automation tasks/month. Browser-provider limits apply.
Issue number,Title,State,Labels,Issue URL
42,Keyboard focus lost,Open,bug; accessibility,https://example.com/repo/issues/42
47,Add export help,Open,documentation,https://example.com/repo/issues/47
Three small steps.
- 01
Get WebAct ready.
Install the Chrome extension and verify your WebAct account. Choose Browser model → ChatGPT and sign in when prompted.
- 02
Bring the right context.
Open the repository’s Issues page. Apply the state, label or assignee filters you need, then select up to 25 readable issue rows. Activate WebAct on that tab and choose Task mode.
- 03
Paste. Run. Check.
Review the proposed actions, run the task, then check the output against the source before using it.
A GitHub issue snapshot for a triage meeting.
Use a CSV when you need a short issue list alongside planning notes. Keeping the issue number and URL together makes it possible to return to the original discussion. Visible labels can be kept as text without guessing priority or severity.
Start from GitHub’s Issues page and set the filters before selecting the source. A result count can include issues that are not loaded on the page. The export should report the rows it actually included, not copy that total as its coverage.
What you bring.
a filtered GitHub Issues page with a readable selection of issue rows.
What you get.
Turn a selected GitHub issue list into CSV with issue numbers, titles, labels and links. CSV file.
Keep it focused.
One active tab; up to 25 records or one short document to start. Generated files must stay under 48,000 UTF-8 bytes.
Give the busywork to WebAct.
Copy this task and paste it into WebAct on your source page.
GitHub Issues to CSVTASKExport only the selected GitHub issue rows to CSV with columns Issue number, Title, State, Labels and Issue URL. Preserve issue numbers as text and use actual issue links. Join multiple visible labels with semicolons. Include state only if observed or explicitly established by the current filter. Do not open issues, fetch comments, paginate, infer severity or modify repository data. Work in this one activated tab only, with up to 25 readable records or one short document. Do not modify the source. Stop and explain if the selected content is unreadable or incomplete. Create a CSV file named webact-github-issues-to-csv.csv. Keep the complete file under 48,000 UTF-8 bytes. Report the source coverage and verify the actual download before claiming completion. Keep one header row, consistent columns, escaped quotes and literal spreadsheet-safe text. Ask me for any required settings or source facts that are missing before starting. Start with up to 25 records or one short document. Report exactly which source content was included.
Paste in Task mode with Browser model selected.
Make it yours. Specify the repository and filters for the snapshot. Ask for issue numbers and URLs; add assignee or milestone only when those details are readable.
Before you start.
Two open issues preserve exact numbers, labels and source links without adding severity.
Chat or Task? Choose your modeDoes this export every issue in a repository?
No. This recipe is for a small readable selection on the current page. It does not paginate through the repository or collect comments. For a bulk export, consider GitHub CLI or API-based export tools.
Can I choose only open bugs or assigned issues?
Apply the relevant GitHub filters first. Then select the readable results and include the filter description in your task. Preserve the actual displayed labels; do not assume an issue is a bug from its title alone.
Does WebAct need a GitHub personal access token?
This page recipe reads the tab you activate and creates a local file, so it does not ask for a GitHub API token. You still need permission to view and share the repository data, and the selected context is processed by your browser AI provider.
Is the CSV ready to import into a project tracker?
It is a reviewable spreadsheet snapshot. A tracker may require its own field mapping, IDs or import format. Review and map the CSV before importing; WebAct does not create or update issues with this task.
What should I check in the result?
Two open issues preserve exact numbers, labels and source links without adding severity. This is one loaded issue-list selection. Other result pages, discussion comments, hidden assignees and issue bodies are excluded unless supplied. No repository token or API integration is used by this recipe.
Can I use this on the Free plan?
Yes. Install the Chrome extension, verify your WebAct account and use an available ChatGPT browser connection in the same Chrome profile. Free includes 25 user-started automation tasks per calendar month (UTC), shared across all tools. A task counts when its first action starts; steps and necessary retries within that task do not count separately. Provider limits apply. After 25 tasks, upgrade or wait for the reset.
Does this page run the task?
This page provides an illustrative example and a task to copy. Run it through WebAct on the source page you activate. Selected page context is processed by your browser AI provider. An ordinary answer in browser Chat uses no WebAct automation allowance; creating a file or changing fields in Task mode does.
Further reading: Zapier: GitHub and Google Sheets integration · GitHub: Filtering and searching issues and pull requests. These sources describe native features, user questions or broader workflows; this page covers the selected browser task above. WebAct is independent of the named services.
Learn how shared page context is handled in our privacy policy.
A little more room for your work.
Bring WebAct to the page you’re already working on.