--- title: Marketing ops as code: Automating events from planning... description: A GitHub marketing lead in Japan and Korea describes automating the entire event lifecycle (landing pages, UTM links, invitations, registrant screening, CRM... canonical: https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Marketing ops as code: Automating events from planning to follow-up on GitHub | daily.dev og:description: A GitHub marketing lead in Japan and Korea describes automating the entire event lifecycle (landing pages, UTM links, invitations, registrant screening, CRM... og:url: https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo og:image: https://api.daily.dev/og/posts/WB5PbGvMo.png og:image:alt: Marketing ops as code: Automating events from planning to follow-up on GitHub og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Marketing ops as code: Automating events from planning to follow-up on GitHub **[GitHub Blog](https://daily.dev/sources/ghblog)** · 12 min read · 0 upvotes · 0 comments ## Summary A GitHub marketing lead in Japan and Korea describes automating the entire event lifecycle (landing pages, UTM links, invitations, registrant screening, CRM uploads, and reports) using GitHub Issues, labels, GitHub Actions, and GitHub Copilot. The system relies on issue forms as structured intake, labels as triggers, an AGENTS.md runbook file, Copilot agent skills written as SKILL.md files, a DRY_RUN switch for safe testing, and built-in guardrails like secret scanning push protection and Copilot's no-retention data policy. The author frames this as a template anyone with repetitive, API-accessible work can replicate by writing down their runbooks. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is a SKILL.md file in GitHub Copilot and how does it work? A SKILL.md file is a written procedure in plain Markdown that tells GitHub Copilot what to do, in what order, and what to watch out for, functioning like an agent skill. It lets non-fixed, flexible workflows (like market-specific post-event follow-up) be executed by Copilot without hard-coding logic, and new skills go through pull request review with a CODEOWNERS file routing approvals. _Teams turning runbooks into repeatable AI-driven workflows can find implementation write-ups like this on daily.dev._ ### How can I prevent GitHub Copilot automation from accidentally leaking API secrets into a repository? GitHub's secret scanning with push protection blocks a push before a detected secret ever lands in the repository, and for GitHub's own tokens, any that slip through are revoked automatically. This guardrail, combined with a DRY_RUN repository variable that lets every workflow run without touching external systems, allows safe experimentation with automation that touches customer data and credentials. _Developers wiring up automation with sensitive credentials can track guardrail practices like these via daily.dev._ ## Similar posts on daily.dev - [From coder to orchestrator: How agents shift the role of a developer](https://daily.dev/posts/from-coder-to-orchestrator-how-agents-shift-the-role-of-a-developer-sk2e3cswg) · GitHub Blog · 2 upvotes · 0 comments - [7 Set & Forget AI Automations for Marketers](https://daily.dev/posts/7-set-forget-ai-automations-for-marketers-2ea0g0j42) · Kilo Blog · 2 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#ai-agents](https://daily.dev/tags/ai-agents), [#automation](https://daily.dev/tags/automation), [#github-actions](https://daily.dev/tags/github-actions) [View this post on daily.dev](https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Marketing ops as code: Automating events from planning to follow-up on GitHub","url":"https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo"},"datePublished":"2026-09-11T18:27:54.676Z","dateModified":"2026-09-11T18:28:18.834Z","description":"A GitHub marketing lead in Japan and Korea describes automating the entire event lifecycle (landing pages, UTM links, invitations, registrant screening, CRM...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/023a3a90cfdaeca7d7a28bf56ae1a552?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/023a3a90cfdaeca7d7a28bf56ae1a552?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/106cf162b88840808484d4b5429b59b1","url":"https://daily.dev/sources/ghblog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,ai-agents,automation,github-actions","timeRequired":"PT12M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Blog","item":"https://daily.dev/sources/ghblog"},{"@type":"ListItem","position":3,"name":"Marketing ops as code: Automating events from planning to follow-up on GitHub"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/marketing-ops-as-code-automating-events-from-planning-to-follow-up-on-github-wb5pbgvmo#faq","mainEntity":[{"@type":"Question","name":"What is a SKILL.md file in GitHub Copilot and how does it work?","acceptedAnswer":{"@type":"Answer","text":"A SKILL.md file is a written procedure in plain Markdown that tells GitHub Copilot what to do, in what order, and what to watch out for, functioning like an agent skill. It lets non-fixed, flexible workflows (like market-specific post-event follow-up) be executed by Copilot without hard-coding logic, and new skills go through pull request review with a CODEOWNERS file routing approvals. Teams turning runbooks into repeatable AI-driven workflows can find implementation write-ups like this on daily.dev."}},{"@type":"Question","name":"How can I prevent GitHub Copilot automation from accidentally leaking API secrets into a repository?","acceptedAnswer":{"@type":"Answer","text":"GitHub's secret scanning with push protection blocks a push before a detected secret ever lands in the repository, and for GitHub's own tokens, any that slip through are revoked automatically. This guardrail, combined with a DRY_RUN repository variable that lets every workflow run without touching external systems, allows safe experimentation with automation that touches customer data and credentials. Developers wiring up automation with sensitive credentials can track guardrail practices like these via daily.dev."}}]} ```