Container Registry — Animate | AI Wisdom

← Back to topic
🎞 ANIMATE · Mode 3 of 5 · +100 XP— Container Registry
📋Trigger
⚙️Metadata
🔄Auth
✅Push
🎯 Next: Test →
Step 1 / 4
Speed
Trigger Events & Permissions
on: push to main AND version tags; packages: write permission for GHCR💡 Analogy
Like having a key card that only unlocks the specific doors you need.
Trigger on main pushes and semantic version tags (v1.2.3). The packages: write permission is required to push to GitHub Container Registry.
Console Output
> push to main → workflow triggered
> push v1.2.3 tag → workflow triggered
> permissions: packages:write granted ✅
●registry.yml
Trigger Events & PermissionsL2–12
1# GitHub Actions: build, tag, push to GitHub Container Registry (GHCR)
2name: Build and Push Image
3on:
4  push:
5    branches: [main]
6    tags: ['v*.*.*']             # also trigger on version tags
7 
8jobs:
9  build:
10    runs-on: ubuntu-latest
11    permissions:
12      contents: read
13      packages: write            # needed to push to GHCR
14    steps:
15      - uses: actions/checkout@v4
16 
17      # Extract metadata: tags & labels from git refs
18      - id: meta
19        uses: docker/metadata-action@v5
20        with:
21          images: ghcr.io/${{ github.repository }}
22          tags: |
23            type=sha                     # ghcr.io/org/app:abc1234
24            type=semver,pattern={{version}} # ghcr.io/org/app:1.2.3
25            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
26 
27      - uses: docker/login-action@v3
28        with:
29          registry: ghcr.io
30          username: ${{ github.actor }}
31          password: ${{ secrets.GITHUB_TOKEN }}
32 
33      - uses: docker/build-push-action@v5
34        with:
35          push: true
36          tags: ${{ steps.meta.outputs.tags }}
37          labels: ${{ steps.meta.outputs.labels }}
38          cache-from: type=gha
39          cache-to: type=gha,mode=max
40          platforms: linux/amd64,linux/arm64  # multi-arch
40 lines
Timeline — 4 Steps
Trigger Events & Permissions
on: push to main AND version tags; packages: write permission for GHCR💡 Analogy
Like having a key card that only unlocks the specific doors you need.
Trigger on main pushes and semantic version tags (v1.2.3). The packages: write permission is required to push to GitHub Container Registry.
Console Output
> push to main → workflow triggered
> push v1.2.3 tag → workflow triggered
> permissions: packages:write granted ✅

Was this page helpful?

Discussion

on: push to main AND version tags; packages: write permission for GHCR

💡 Analogy

Like having a key card that only unlocks the specific doors you need.

Trigger on main pushes and semantic version tags (v1.2.3). The packages: write permission is required to push to GitHub Container Registry.

Console Output

> push to main → workflow triggered
> push v1.2.3 tag → workflow triggered
> permissions: packages:write granted ✅

on: push to main AND version tags; packages: write permission for GHCR

💡 Analogy

Like having a key card that only unlocks the specific doors you need.

Trigger on main pushes and semantic version tags (v1.2.3). The packages: write permission is required to push to GitHub Container Registry.

Console Output

> push to main → workflow triggered
> push v1.2.3 tag → workflow triggered
> permissions: packages:write granted ✅