Separate concerns properly:
- Badge updates: run on all branches to keep documentation accurate
- Docker builds: only on main branch for production deployments
This follows best practices where documentation should be updated
regardless of branch, but deployments only happen from main.
- Fix badge URLs and remove duplicates
- Add update-all-badges.sh script for single commit updates
- Update CI/CD workflow to use environment variables
- Remove complex sequential commit logic
- Follow KISS principle with simple env var approach
- Fix step pattern escaping in pkg/bdd/steps/steps.go:80
- Update CI/CD workflow to use run-bdd-tests.sh script
- Enhance run-bdd-tests.sh for both local and CI environments
- Add strict validation for undefined/pending/skipped steps
- Update BDD testing documentation with pattern requirements
The CI/CD pipeline now properly validates BDD tests and fails on any
undefined, pending, or skipped steps. All 22 BDD scenarios are passing
with correct step pattern registration.
- Bypass Docker entirely for Swagger generation
- Test if issue is Docker-specific or workspace-related
- Simplest possible approach to isolate the problem
- Remove -w flags that conflict with Gitea's auto-generated mounts
- Let Docker Compose use default working directory from docker-compose.yml
- Align with Gitea Actions volume mounting best practices
- Override docker-compose.yml volume with explicit host path
- Mount full repository root to /workspace in container
- Simplifies debugging and ensures go.mod is accessible
- Add debug step to check workspace directory structure
- Add pwd and ls commands to Swagger generation step
- Helps diagnose go.mod file not found issue
- Set GOPATH environment variable to workspace root
- Allow go generate to find go.mod from parent directories
- Fixes go.mod file not found error in CI workflow
- Change working directory approach for go generate command
- Run from root workspace but cd to pkg/server for execution
- Fixes go.mod file not found error in CI workflow
- Remove unnecessary go mod tidy execution when using Docker cache
- Dependencies are already pre-installed in the cache image
- Only run go mod tidy when not using cache (native execution)
- This leverages the true purpose of the Docker build cache
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
- Add go mod tidy step to match local script
- Execute build.sh script in Docker Compose container
- Maintain consistent build process between local and CI
- Ensure Docker cache compatibility
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
- Replace docker run commands with docker compose
- Use separate docker-compose.build.yml for build cache
- Maintain PostgreSQL service with Docker Compose
- Ensure consistent container networking
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
