Skip to content

ci(build-main): add manual workflow_dispatch trigger for main#525

Merged
Zheaoli merged 1 commit into
mainfrom
ci-manual-main-deploy
Jun 10, 2026
Merged

ci(build-main): add manual workflow_dispatch trigger for main#525
Zheaoli merged 1 commit into
mainfrom
ci-manual-main-deploy

Conversation

@Zheaoli

@Zheaoli Zheaoli commented Jun 10, 2026

Copy link
Copy Markdown
Collaborator

What

Adds a manual trigger to the Latest image workflow (build-main.yaml) so the current main can be built and pushed to Docker Hub on demand, without cutting a v* tag.

  • Add workflow_dispatch: alongside the existing push: tags: ['v*'] trigger. From the Actions tab you can now run it manually (defaults to the main branch) → builds the multi-arch image and pushes picimpact:latest. The server then pulls :latest.
  • Drop the Get Version step: build-main hardcodes the picimpact:latest tag and never referenced its VERSION output, so it was dead code — and under a manual (non-tag) run ${GITHUB_REF#refs/tags/} would resolve to a branch ref, which is misleading. Removing it keeps the manual run clean.

Scope / not changed

  • The image tag stays :latest (the deployable tag this workflow already produces).
  • The versioned release workflow (build-release.yaml, v* tags → picimpact:<version>) is untouched.
  • No server-side deploy logic added — this only builds + pushes the image (existing buildx → Docker Hub), as scoped.

Verify

After merge: GitHub → Actions → "Latest Docker Multi-arch Image CI & CD" → Run workflow (branch main) → confirms a fresh picimpact:latest is built and pushed.

The Latest image workflow only fired on `v*` tags, so there was no way to
build and push the `:latest` image from the current `main` without cutting
a version tag. Add a `workflow_dispatch` trigger (alongside the existing
tag trigger) so `main` can be built and pushed to Docker Hub on demand from
the Actions tab.

Also drop the `Get Version` step: build-main hardcodes the
`picimpact:latest` tag and never referenced its `VERSION` output, so it was
dead — and under a manual (non-tag) run `${GITHUB_REF#refs/tags/}` would
resolve to a branch ref, which is misleading. Removing it keeps the manual
run clean. The versioned release workflow (`build-release.yaml`, `v*` tags)
is untouched.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
picimpact Ready Ready Preview, Comment Jun 10, 2026 1:37pm

@Zheaoli Zheaoli merged commit a58d0bc into main Jun 10, 2026
6 checks passed
@Zheaoli Zheaoli deleted the ci-manual-main-deploy branch June 10, 2026 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant