codex - added docu
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
# 02 Project Repository Connections
|
||||
|
||||
## Goal
|
||||
|
||||
Allow projects to store one or more Gitea repository connections through project settings.
|
||||
|
||||
## Requirements
|
||||
|
||||
- Add project settings for repository connections.
|
||||
- A repository connection must store enough information to identify the provider and repository.
|
||||
- The first supported provider is Gitea.
|
||||
- A project may have multiple repository connections.
|
||||
- Repository connection management must be protected by the appropriate project-level permissions.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- An authorized user can add, edit, list, and remove Gitea repository connections for a project.
|
||||
- A project can hold more than one repository connection.
|
||||
- Repository connections are clearly scoped to their project.
|
||||
- The stored data is compatible with the provider abstraction introduced in release `0.2`.
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Automatic repository discovery
|
||||
- Cross-project shared repository connections
|
||||
- Provider credential vault design beyond what is necessary for the first working Gitea integration
|
||||
Reference in New Issue
Block a user