Trigger redeploy after image push
Build & Push / Lint & Build (push) Successful in 1m16s
Build & Push / Build & Push Image (push) Successful in 28s
Build & Push / Trigger Deploy (push) Successful in 1s

- Add deploy job to docker workflow: POST redeploy webhook once the image is pushed (fixes push-webhook race)

- README: fix CI/CD tag docs
This commit is contained in:
fristy committed 2026-09-10 14:48:22 +03:00
1 parent bcc5662a44
commit 66be7a71a7
2 files changed
+11 -2

No files matched your search

+10
View File
@@ -75,3 +75,13 @@ jobs:
push: true push: true
tags: ${{ steps.meta.outputs.tags }} tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }} labels: ${{ steps.meta.outputs.labels }}
deploy:
name: Trigger Deploy
needs: image
if: github.ref == 'refs/heads/main'
runs-on: ubuntu-latest
steps:
- name: Trigger Deploy
run: |
curl --fail -X POST "${{ secrets.WEBHOOK_URL }}"
+1 -2
View File
@@ -50,10 +50,9 @@ docker pull git.fristy.net/fristy/fristynet:latest
## CI/CD ## CI/CD
Pushes to `main` (and `v*` tags) run format check, lint and build first. If those pass, the Docker image is built and pushed to the Gitea registry: Pushes to `main` (and `<sha>` tags) run format check, lint and build first. If those pass, the Docker image is built and pushed to the Gitea registry:
- `git.fristy.net/fristy/fristynet:latest` on every `main` push - `git.fristy.net/fristy/fristynet:latest` on every `main` push
- `git.fristy.net/fristy/fristynet:<version>` on tags like `v1.2.0`
- `git.fristy.net/fristy/fristynet:<sha>` for every pushed commit - `git.fristy.net/fristy/fristynet:<sha>` for every pushed commit
Pull requests only run the checks — nothing is pushed. Pull requests only run the checks — nothing is pushed.