How to export selected GitHub issues for a triage review
A GitHub issue spreadsheet helps a team compare selected reports outside the issue list. Stable issue numbers and links make the exported rows useful for returning to the original discussion.
Start with the right material.
- What you provide
- a filtered GitHub Issues page with a readable selection of issue rows.
- The intended result
- Turn a selected GitHub issue list into CSV with issue numbers, titles, labels and links.
How the workflow works.
Choose the fields needed for triage and preserve repository context with each issue identifier. Keep labels, state and assignee information as observed, leaving missing values explicit.
What to check in the result.
Compare the row set with the selected issues. A visible list may cover only part of a search or repository, and an export does not change issue labels, ownership or state.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Issue number, Title, State, Labels, Issue URL. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.