How to prepare a CSV review of selected GitHub pull requests
A pull-request table helps a reviewer compare selected work across titles, authors, states and references. Repository context keeps identifiers meaningful when the file leaves GitHub.
Start with the right material.
- What you provide
- selected loaded pull-request rows on GitHub.
- The intended result
- Selected pull-request rows with visible status and links.
How the workflow works.
Choose the fields needed for the review and record their displayed values. Keep open, closed and merged states distinct rather than treating all closed requests as shipped changes.
What to check in the result.
Compare the selection with the exported rows and confirm ambiguous dates. The table describes readable PR metadata; it does not establish code quality, test success or deployment status.
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: Number, Title, Author, State, Review status, 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.