GitHub Actions — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— GitHub Actions CI/CD
📋Trigger
⚙️Jobs
🔄Dependencies
✅Docker
🎯 Next: Test →
Step 1 / 4
Speed
Trigger Events
on: push to main/develop, PR to main — control when the pipeline runs💡 Analogy
Like an alarm system — specify exactly which "sensor events" trigger a response.
The "on" section defines when the workflow runs. Push to main or develop triggers CI. PRs to main also trigger to validate before merging.
Console Output
> push to "main" → workflow triggered
> pull_request to "main" → workflow triggered
> push to "feature/xyz" → NOT triggered
●.github/workflows/ci.yml
Trigger EventsL2–7
1name: CI/CD Pipeline
2on:
3  push:
4    branches: [main, develop]
5  pull_request:
6    branches: [main]
7 
8jobs:
9  test:
10    runs-on: ubuntu-latest
11    steps:
12      - uses: actions/checkout@v4
13      - uses: actions/setup-node@v4
14        with: { node-version: '20', cache: 'npm' }
15      - run: npm ci
16      - run: npm test -- --coverage
17      - uses: codecov/codecov-action@v4
18 
19  build-push:
20    needs: [test]                           # wait for test job
21    runs-on: ubuntu-latest
22    if: github.ref == 'refs/heads/main'     # only on main
23    permissions:
24      contents: read
25      packages: write
26    steps:
27      - uses: actions/checkout@v4
28      - uses: docker/login-action@v3
29        with:
30          registry: ghcr.io
31          username: ${{ github.actor }}
32          password: ${{ secrets.GITHUB_TOKEN }}
33      - uses: docker/build-push-action@v5
34        with:
35          push: true
36          tags: ghcr.io/${{ github.repository }}:${{ github.sha }}
37          cache-from: type=gha
38          cache-to: type=gha,mode=max
38 lines
Timeline — 4 Steps
Trigger Events
on: push to main/develop, PR to main — control when the pipeline runs💡 Analogy
Like an alarm system — specify exactly which "sensor events" trigger a response.
The "on" section defines when the workflow runs. Push to main or develop triggers CI. PRs to main also trigger to validate before merging.
Console Output
> push to "main" → workflow triggered
> pull_request to "main" → workflow triggered
> push to "feature/xyz" → NOT triggered

Was this page helpful?

Discussion

on: push to main/develop, PR to main — control when the pipeline runs

💡 Analogy

Like an alarm system — specify exactly which "sensor events" trigger a response.

The "on" section defines when the workflow runs. Push to main or develop triggers CI. PRs to main also trigger to validate before merging.

Console Output

> push to "main" → workflow triggered
> pull_request to "main" → workflow triggered
> push to "feature/xyz" → NOT triggered

on: push to main/develop, PR to main — control when the pipeline runs

💡 Analogy

Like an alarm system — specify exactly which "sensor events" trigger a response.

The "on" section defines when the workflow runs. Push to main or develop triggers CI. PRs to main also trigger to validate before merging.

Console Output

> push to "main" → workflow triggered
> pull_request to "main" → workflow triggered
> push to "feature/xyz" → NOT triggered