Add Go module verification and build steps to CI workflow
Some checks failed
CI/CD Pipeline / backend-lint (push) Failing after 31s
CI/CD Pipeline / backend-build (push) Has been skipped
CI/CD Pipeline / frontend-lint (push) Successful in 1m37s
CI/CD Pipeline / frontend-build (push) Failing after 37s
CI/CD Pipeline / e2e-test (push) Has been skipped

- Introduce a verification step for Go module setup to ensure proper configuration
- Add a build step to populate the Go module cache before running vet commands
- Maintain existing environment variable settings for consistency
This commit is contained in:
Damir Mukimov 2025-12-26 13:14:20 +01:00
parent f751706372
commit a504795071
No known key found for this signature in database
GPG Key ID: 42996CC7C73BC750

View File

@ -81,6 +81,24 @@ jobs:
GO111MODULE: on GO111MODULE: on
GOPROXY: https://proxy.golang.org,direct GOPROXY: https://proxy.golang.org,direct
GOSUMDB: sum.golang.org GOSUMDB: sum.golang.org
- name: Verify module setup
working-directory: bugulma/backend
run: |
pwd
ls -la go.mod
go list -m
go list ./pkg/config
env:
GO111MODULE: on
GOPROXY: https://proxy.golang.org,direct
GOSUMDB: sum.golang.org
- name: Build module to populate cache
working-directory: bugulma/backend
run: go build ./...
env:
GO111MODULE: on
GOPROXY: https://proxy.golang.org,direct
GOSUMDB: sum.golang.org
- name: Vet - name: Vet
working-directory: bugulma/backend working-directory: bugulma/backend
run: go vet ./... run: go vet ./...