6 Commits

Include renames

Author	SHA1	Message	Date
arcodange	183933b43e	feat: integrate swag fmt and improve CI/CD workflows ... - Add swag fmt to git pre-commit hook and CI/CD pipeline - Create comprehensive CONTRIBUTING.md guide with AI section - Update ADR-0013 with swag fmt documentation - Fix swagger generation to include all endpoints - Improve local testing scripts and workflows - Update Dockerfile for better swagger handling - Fix CI/CD workflow file references	2026-04-06 15:36:55 +02:00
arcodange	a15f651bae	🗑️ chore: remove workflow-validation job ... Remove redundant workflow-validation job: - Local validation script is sufficient - Simplifies CI workflow - Reduces CI execution time - Removes potential failure point Workflow validation now handled locally before pushing to repository.	2026-04-06 13:17:29 +02:00
arcodange	370fbdf72f	🐛 fix: resolve CI workflow issues ... Fix three critical CI issues: 1. SWAG TOOL: Install swag before go generate - Adds 'Install swag' step to build-test job - Prevents 'command not found' errors - Ensures swagger docs can be generated 2. GO VET REDUNDANCY: Remove duplicate go vet - Removes go vet from lint-format job - Keeps go vet only in build-test job - Reduces CI execution time 3. WORKFLOW VALIDATION: Fix yamllint path - Updates validate-workflow.sh to use absolute paths - Fixes .yamllint.yaml file not found error - Makes path resolution more robust These fixes address the root causes of: - Job 350 failure (missing swag) - Redundant validation (duplicate go vet) - Workflow validation failures (wrong paths) Tested locally and ready for CI.	2026-04-06 12:53:43 +02:00
arcodange	6d18d5b728	🐛 fix: add swagger docs generation to CI workflow ... Fix CI/CD workflow failure by adding swagger documentation generation step before building packages. The workflow was failing with: pkg/server/server.go:30:12: pattern docs/swagger.json: no matching files found Root cause: The //go:embed directive requires generated swagger docs but the workflow didn't generate them before building. Solution: Added 'Generate Swagger Docs' step: - name: Generate Swagger Docs run: cd pkg/server && go generate Also generated the missing docs locally to fix immediate issue: cd pkg/server && go generate This ensures swagger.json, swagger.yaml, and docs.go are created before the build step, preventing the embed directive from failing.	2026-04-06 12:34:42 +02:00
arcodange	7c6075e836	🤖 feat: simplify CI/CD structure and add Docker workflow ... - Rename ci-cd.yaml to go-ci-cd.yaml for clarity - Add dockerimage.yaml workflow for Docker builds - Create Dockerfile for production deployment - Add comprehensive CI/CD documentation - Create contributor-quickstart.sh for easy validation - Update all scripts to handle both workflow files - Fix event triggers to run on all relevant pushes - Remove redundant YAML syntax validation - Improve workflow validation for Arcodange conventions BREAKING CHANGE: ci-cd.yaml renamed to go-ci-cd.yaml See scripts/cicd/README.md for complete documentation. Generated by Mistral Vibe. Co-Authored-By: Mistral Vibe <[email protected]>	2026-04-06 11:02:36 +02:00
arcodange	b391534f2d	🤖 feat: implement trunk-based CI/CD with local testing ... - Designed trunk-based development workflow with branch protection - Added workflow validation job to prevent main branch breaks - Integrated act (GitHub Actions runner) for local Gitea workflow testing - Created unified CI/CD script interface (scripts/cicd.sh) - Added YAML lint configuration with practical limits (400 chars) - Organized all CI/CD scripts under scripts/cicd/ directory - Confirmed Gitea/GitHub Actions compatibility via local testing - Updated ADR 0017 with implementation details and test results - Enhanced documentation with local development workflow See ADR-0017 for complete trunk-based development workflow documentation. See ADR-0016 for CI/CD pipeline design.	2026-04-05 23:07:32 +02:00