CI/CD Workflow #11

New issue

Closed

opened 2026-02-02 19:58:46 +01:00 by qwc · 1 comment

qwc commented

2026-02-02 19:58:46 +01:00

Owner

Set up CI/CD pipeline for the project:

Run go test -mod=vendor ./... on push
Build binary to verify compilation
Lint with go vet
Build Docker image on tag/release

Should use Forgejo Actions (Gitea Actions compatible with GitHub Actions syntax).

Set up CI/CD pipeline for the project: - Run `go test -mod=vendor ./...` on push - Build binary to verify compilation - Lint with `go vet` - Build Docker image on tag/release Should use Forgejo Actions (Gitea Actions compatible with GitHub Actions syntax).

qwc commented

2026-02-02 20:44:04 +01:00

Author

Owner

Implemented in f602417:

Created .forgejo/workflows/ci.yml with Forgejo Actions:

test job: runs go test -mod=vendor -count=1 ./... in golang:1.24-alpine
build job: runs CGO_ENABLED=0 go build -mod=vendor -ldflags="-s -w" to verify compilation
docker job: builds Docker image on main branch pushes

Triggers on push to main and pull requests.

Implemented in f602417: Created `.forgejo/workflows/ci.yml` with Forgejo Actions: - **test** job: runs `go test -mod=vendor -count=1 ./...` in golang:1.24-alpine - **build** job: runs `CGO_ENABLED=0 go build -mod=vendor -ldflags="-s -w"` to verify compilation - **docker** job: builds Docker image on main branch pushes Triggers on push to main and pull requests.

qwc closed this issue

2026-02-02 20:44:09 +01:00

qwc referenced this issue

2026-05-18 20:07:28 +02:00

Fix inline authz drift (H-1, H-2) and project-scoped tokens creating projects (H-3) #106