How does the Postmortem Pack GitHub Action attach timelines to issues?
The `attach-timeline` composite action installs IncidentScribe via pip, runs `incidentscribe render` on a JSONL path you provide, uploads the output as a workflow artifact, and optionally posts the rendered Markdown as a comment on a GitHub…
How does the Postmortem Pack GitHub Action attach timelines to issues?
Answer
The `attach-timeline` composite action installs IncidentScribe via pip, runs `incidentscribe render` on a JSONL path you provide, uploads the output as a workflow artifact, and optionally posts the rendered Markdown as a comment on a GitHub issue. Inputs include `jsonl-path`, `template` (blameless, exec-summary, or security-incident), `format` for raw timelines, `output-path`, `incidentscribe-install` (default `-e .` from a repo with pyproject.toml), `issue-number`, and `artifact-name`. Comments truncate above 60,000 characters with a notice.
Related workflows
Start with the free IncidentScribe timeline viewer or CLI to validate JSONL exports. The Postmortem Pack adds blameless, executive-summary, and security-incident templates, a two-week team rollout guide, forensic checklist, and a GitHub Action that uploads rendered timelines as workflow artifacts or issue comments.
Next steps
Install the pack from Hermes Plant, run `incidentscribe render session.jsonl --template blameless -o postmortem.md`, and copy `github-action/attach-timeline/` into your repo for CI. Pair with DestructGuard audit logs when approve-or-abort decisions matter for the timeline.
FAQ
How does the Postmortem Pack GitHub Action attach timelines to issues?
The `attach-timeline` composite action installs IncidentScribe via pip, runs `incidentscribe render` on a JSONL path you provide, uploads the output as a workflow artifact, and optionally posts the rendered Markdown as a comment on a GitHub issue. Inputs include `jsonl-path`, `template` (blameless, exec-summary, or security-incident), `format` for raw timelines, `output-path`, `incidentscribe-install` (default `-e .` from a repo with pyproject.toml), `issue-number`, and `artifact-name`. Comments truncate above 60,000 characters with a notice.