# 01 Git Provider Abstraction and Gitea Foundation

## Goal

Introduce the integration foundation in a provider-agnostic way while implementing Gitea as the first actual Git provider.

## Requirements

- Add a Git provider abstraction at the domain and service level.
- Implement Gitea as the first provider.
- Keep the ticketing and project domain free from hard-coded Gitea-specific assumptions wherever possible.
- Design the integration so future providers such as GitHub and GitLab can be added without redesigning project or ticket core models.

## Acceptance Criteria

- The codebase has a clear provider boundary for Git integrations.
- Gitea-specific logic lives behind that boundary.
- Project and ticket core logic depend on the provider abstraction, not directly on Gitea client details.

## Out of Scope

- GitHub integration
- GitLab integration
- Webhook processing for multiple providers