arcodange/dance-lessons-coach
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

🐛 fix: try running go generate directly on host

Browse Source 
- Bypass Docker entirely for Swagger generation

- Test if issue is Docker-specific or workspace-related

- Simplest possible approach to isolate the problem
This commit is contained in:
Gabriel Radureau
2026-04-08 10:17:09 +02:00
parent fc410fdb48
commit 76e3579f06
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.gitea/workflows/ci-cd.yaml
View File

@@ -166,8 +166,8 @@ jobs:
- name: Export DEPS_HASH for Docker Compose - name: Export DEPS_HASH for Docker Compose
run: echo "DEPS_HASH=${{ needs.build-cache.outputs.deps_hash }}" >> $GITHUB_ENV run: echo "DEPS_HASH=${{ needs.build-cache.outputs.deps_hash }}" >> $GITHUB_ENV
- name: Generate Swagger Docs using Docker Compose - name: Generate Swagger Docs directly
run: cd /workspace/arcodange/dance-lessons-coach && docker compose -f docker-compose.build.yml run --rm build-cache sh -c "go generate ./pkg/server/" run: cd /workspace/arcodange/dance-lessons-coach && go generate ./pkg/server/
- name: Build all packages using Docker Compose - name: Build all packages using Docker Compose
run: cd /workspace/arcodange/dance-lessons-coach && docker compose -f docker-compose.build.yml run --rm build-cache sh -c "go build ./..." run: cd /workspace/arcodange/dance-lessons-coach && docker compose -f docker-compose.build.yml run --rm build-cache sh -c "go build ./..."