Safe Follow-Ups from Meeting Transcripts

An example GitHub agentic workflow that automatically processes meeting transcripts and performs follow-up actions on GitHub issues, pull requests, and project boards using AI and safe outputs.

Features

• Automatically triggers on transcript file changes in notes/
• Extracts GitHub issue/PR references from meeting transcripts
• Safely applies decisions: adds comments, labels, and updates Projects v2
• Supports manual triggering with configurable options

Quick Start

1. Add a transcript to notes/YYYY/YYYY-MM-DD-transcript.md:

   # 2026-01-13 Meeting Transcript
   
   **Alex:** We discussed https://github.com/owner/repo/issues/123
   **Blair:** Decision: postpone to next meeting and add label "tsc deferred"

2. Push to main - the workflow automatically runs and applies the decisions

3. View results in GitHub Actions to see what was processed

How It Works

The workflow finds transcript files, extracts GitHub references and decisions, then emits safe outputs:

{"type":"add_comment","target_repo":"owner/repo","target":123,"body":"Meeting decision..."}
{"type":"add_labels","target_repo":"owner/repo","target":123,"labels":["tsc deferred"]}

Development

GitHub Actions secrets

• PROJECTS_GITHUB_TOKEN (required only if you enable project creation/linking in the test workflow): must have Projects v2 write access. A classic PAT needs the project scope; a fine-grained token needs Projects read/write and access to this repository.

After editing transcript-followup.md, recompile:

gh aw compile

Testing: Use the GitHub Actions workflows:

• Create: run the "Setup Test Resources" workflow (file: .github/workflows/setup-test-resources.yml)
• Cleanup: run the "Cleanup Test Resources" workflow (file: .github/workflows/cleanup-test-resources.yml)