---
type: Category
title: GitHub
description: GitHub issues and events as data for issue-driven workflows -- the fields of an issue form, and whether an event's sender is an approver.
tags:
- engineering
generated:
  by: process:tools/catalog/compile.py
  at: '2026-11-13T18:27:40Z'
---

# GitHub

GitHub issues and events as data for issue-driven workflows -- the fields of an issue form, and whether an event's sender is an approver.

- [check-approver](check-approver.md) — Whether a GitHub event's sender is an approver -- one of the people allowed to say "go" to an automated action -- printed as one line naming who approved what, or a failure giving the reason. The approvers file lists one GitHub username per line (# comments; a leading @ or "- " is ignored, so a plain YAML list also works); matching ignores case. label=<name> also requires the event to be that label being applied, so only that label counts as approval. Its receipt is the approval record: which event, which list, which answer.
- [read-issue-form](read-issue-form.md) — The fields of a GitHub issue form as JSON: {"issue": {number, title, author, url, labels}, "fields": {<label_slug>: value}}. GitHub renders a form submission as "### Label" headings with values beneath; each heading becomes a snake_case key, "_No response_" becomes null, and checkbox lists become arrays of the checked options. Accepts a whole GitHub event payload (issues/issue_comment, e.g. $GITHUB_EVENT_PATH) or a bare issue body.
