How to export GitHub issue comments with their references
Issue discussions often contain the evidence behind a technical decision. A comment export is useful when the message sequence, authorship and issue identity remain available for inspection.
Start with the right material.
- What you provide
- one opened GitHub issue with the comments you need expanded.
- The intended result
- Readable issue comments with authors and source links.
How the workflow works.
Capture readable comments in order and preserve code or multiline text within each message. Keep issue and comment references where supplied, distinguishing discussion from state-change events.
What to check in the result.
Check coverage and message boundaries against the thread. An export should not imply that linked logs, private references or unloaded earlier comments were read.
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: Item, Author, Displayed date, Comment, Source 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.