✨ feat(cli): add GIT managment

[vincent-psarga]

Introduce a set of gitsubcommands to manage git providers (called connection, like in the app) and repos.

Could be a first step to manage marketplaces from the cli

[greptile-apps]

Greptile Summary

Adds CLI commands for administering Git connections and repositories, restricts provider/repository creation to organization administrators, and changes distribution tracking to use repositories configured beforehand.

• Adds git connection list/add and git repo list/add CLI command groups with API gateway integration and documentation.
• Maps organization-admin authorization failures to HTTP 403 responses and user-facing CLI messages.
• Stops distribution notifications from implicitly provisioning Git providers or repositories, returning nullable deployment identifiers when no configured repository matches.
• Updates unit, integration, CLI end-to-end, and application end-to-end coverage for the new workflows.

Confidence Score: 5/5

The pull request appears safe to merge because no blocking failure eligible for this follow-up review remains.

No blocking failure remains.

Important Files Changed

Filename	Overview
apps/cli/src/infra/commands/git/addGitRepoHandler.ts	Adds repository parsing, default-branch discovery, repository creation, and permission-aware error reporting.
apps/cli/src/infra/repositories/GitGateway.ts	Adds the CLI HTTP adapter for listing and creating Git providers and repositories.
apps/api/src/app/organizations/git/providers/git-providers.controller.ts	Maps organization-admin authorization failures from provider and repository creation to HTTP 403.
apps/api/src/app/organizations/git/repositories/git-repositories.controller.ts	Maps organization-admin authorization failures during repository creation to HTTP 403.
packages/git/src/application/useCases/addGitProvider/AddGitProviderUseCase.ts	Changes Git provider creation from member-authorized to administrator-authorized execution.
packages/git/src/application/useCases/addGitRepo/AddGitRepoUseCase.ts	Changes managed-repository creation from member-authorized to administrator-authorized execution.
packages/deployments/src/application/services/TargetResolutionService.ts	Resolves targets only from repositories configured beforehand and returns null when none matches.
packages/deployments/src/application/useCases/notifyDistribution/NotifyDistributionUseCase.ts	Skips recording a distribution and returns a null deployment identifier when target resolution finds no configured repository.
packages/deployments/src/application/useCases/notifyArtefactsDistribution/NotifyArtefactsDistributionUseCase.ts	Applies nullable target handling to artifact-distribution notifications.

Sequence Diagram

sequenceDiagram
  participant User
  participant CLI
  participant API
  participant Git as Git domain
  participant Deployments
  User->>CLI: git connection/repo command
  CLI->>API: Organization-scoped request
  API->>Git: List or administer provider/repository
  Git-->>API: Connection/repository result
  API-->>CLI: HTTP response
  CLI-->>User: Formatted result
  User->>CLI: Install/render and notify distribution
  CLI->>API: Distribution notification
  API->>Deployments: Resolve configured repository and target
  alt Repository is configured
    Deployments-->>API: Recorded deployment ID
  else Repository is not configured
    Deployments-->>API: Null deployment ID
  end

Loading

_{Reviews (5): Last reviewed commit: "✅ test(e2e): track repo before asserting..." | Re-trigger Greptile}

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cteyton]

is displayName mandatory or optional?
If 2), is there any risk it'd fail at runtime ?