cardosofelipe/syndarix
1
0
Fork 0
forked from cardosofelipe/fast-next-template
Code Issues 18 Pull Requests Wiki Activity

Configure CI/CD pipelines for Syndarix #15

New Issue
Closed
opened 2025-12-29 23:45:58 +00:00 by cardosofelipe · 0 comments
cardosofelipe commented 2025-12-29 23:45:58 +00:00
Owner
Copy Link

Description

Set up Gitea Actions CI/CD pipeline for the Syndarix repository.

Requirements

Backend Pipeline

  • Run uv run ruff check app (linting)
  • Run uv run mypy app (type checking)
  • Run IS_TEST=True uv run pytest --cov=app (tests with coverage)
  • Coverage threshold: 90% for new code

Frontend Pipeline

  • Run npm run lint (ESLint)
  • Run npm run type-check (TypeScript)
  • Run npm test (Jest unit tests)

Pipeline Structure

  1. lint job (fast feedback)
  2. test job (depends on lint)
  3. build job (depends on test)
  4. deploy job (only on main, depends on build)

Acceptance Criteria

  • .gitea/workflows/ci.yaml created
  • Backend linting, typing, and tests pass
  • Frontend linting, typing, and tests pass
  • Coverage reports generated
  • Pipeline fails on any check failure
  • Documentation updated

Technical Notes

  • Use uv for Python dependency management
  • Reference: ADR-003 (Celery/Redis architecture)

Assignable To

devops-engineer agent

## Description Set up Gitea Actions CI/CD pipeline for the Syndarix repository. ## Requirements ### Backend Pipeline - Run `uv run ruff check app` (linting) - Run `uv run mypy app` (type checking) - Run `IS_TEST=True uv run pytest --cov=app` (tests with coverage) - Coverage threshold: 90% for new code ### Frontend Pipeline - Run `npm run lint` (ESLint) - Run `npm run type-check` (TypeScript) - Run `npm test` (Jest unit tests) ### Pipeline Structure 1. `lint` job (fast feedback) 2. `test` job (depends on lint) 3. `build` job (depends on test) 4. `deploy` job (only on main, depends on build) ## Acceptance Criteria - [ ] `.gitea/workflows/ci.yaml` created - [ ] Backend linting, typing, and tests pass - [ ] Frontend linting, typing, and tests pass - [ ] Coverage reports generated - [ ] Pipeline fails on any check failure - [ ] Documentation updated ## Technical Notes - Use `uv` for Python dependency management - Reference: ADR-003 (Celery/Redis architecture) ## Assignable To devops-engineer agent
cardosofelipe added the devopsphase-0 labels 2025-12-29 23:49:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
Agent orchestration
 architecture
Architectural decisions
 backend
Backend work
 blocked
Blocked by dependency
 database
Database/migrations
 design
UI/UX design work
 devops
DevOps/Infrastructure work
 epic
Epic/parent issue
 frontend
Frontend work
 infrastructure
Infrastructure / DevOps
 mcp
MCP related
 phase-0
Phase 0: Foundation
 phase-1
Phase 1: Core Platform
 phase-2
Phase 2: MCP Integration
 priority:high
High priority
 spike
Architecture spike / research task
No Label devops phase-0
Milestone
No items
No Milestone
Assignees
Clear assignees
cardosofelipe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cardosofelipe/syndarix#15
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?