fix: Add explicit module checks and GO111MODULE env before vet
Some checks failed
CI/CD Pipeline / frontend-lint (push) Failing after 28s
CI/CD Pipeline / frontend-build (push) Has been skipped
CI/CD Pipeline / backend-lint (push) Failing after 44s
CI/CD Pipeline / backend-build (push) Has been skipped
CI/CD Pipeline / e2e-test (push) Has been skipped

- Set GO111MODULE=on explicitly to ensure module mode
- Add go list -m and go list ./pkg/config to verify module recognition
- This should help diagnose why Go isn't recognizing the module in CI
This commit is contained in:
Damir Mukimov 2025-12-24 23:11:32 +01:00
parent 03eb4f08a6
commit e9f6751807
No known key found for this signature in database
GPG Key ID: 42996CC7C73BC750

View File

@ -75,10 +75,13 @@ jobs:
run: go mod download run: go mod download
- name: Vet - name: Vet
working-directory: bugulma/backend working-directory: bugulma/backend
env:
GO111MODULE: on
run: | run: |
go mod tidy go mod tidy
go mod verify go mod verify
go build ./... || true go list -m
go list ./pkg/config
go vet ./... go vet ./...
- name: Test - name: Test
working-directory: bugulma/backend working-directory: bugulma/backend