GitHub's Japan marketing lead turns event ops into code: one Issue stages the whole pipeline

GitHub Blog AI/ML · rss · 2026-09-12

GitHub's marketing lead for Japan/Korea, a former ops engineer, describes automating repetitive event operations with GitHub Copilot: what used to take two days of manual setup now runs from a single GitHub Issue—duplicating the landing page, generating the full set of UTM-tagged links, drafting the invitation email, updating project boards, daily registrant-list cleaning, and post-event CRM prep and reporting.

The design: Issue Forms as structured application forms, Labels as triggers, GitHub Actions as the machinery. An AGENTS.md runbook at the repo root encodes naming rules and email templates, so Copilot drafts within conventions while humans only sign off. A cron workflow screens registrants every morning, including waitlist checks (enterprise developer vs. student vs. competitor) for invite-only events. A global DRYRUN switch lets him safely test the pipeline end to end.

He argues this beats packaged marketing-automation tools for APAC's fragmented sub-markets: changing the workflow is just a pull request. The only prerequisite is a scriptable way in—an API or a CLI.

Original post →

More from coding & agent

coding & agent channel →