CodeOath
← All posts
CI/CD & DevOps60 min total · 17 parts

CI/CD Pipelines Explained: From git push to Production

Contents — Part 6 of 17: Triggers: What Actually Starts a Run
Part 6 of 17 · ~1 min

Triggers: What Actually Starts a Run

A pipeline can be kicked off by more than "someone pushed code":

on:
  push:
    branches: [main]
  pull_request:
  schedule:
    - cron: "0 3 * * *"     # nightly at 3am UTC — e.g., a full regression suite
  workflow_dispatch:         # manual trigger, with optional inputs, from the CI UI
  release:
    types: [published]

Scheduled triggers are how teams run something too slow or too expensive to run on every single push — a full end-to-end suite, a dependency vulnerability scan, a nightly performance benchmark — without blocking every developer's feedback loop on it. workflow_dispatch (or the equivalent manual trigger on other platforms) is how a genuinely manual step, like "deploy this specific tag to production right now," stays inside the same auditable pipeline system instead of becoming an ad hoc script someone runs from their laptop.