Add v0.3 GitHub integration release plan and tickets
This commit is contained in:
+26
@@ -0,0 +1,26 @@
|
||||
# 02 User GitHub Connections and Repository Discovery
|
||||
|
||||
## Goal
|
||||
|
||||
Allow a user to connect GitHub in settings and expose the repositories that user can read through the chosen token.
|
||||
|
||||
## Requirements
|
||||
|
||||
- Add GitHub as an option in user Git connection settings.
|
||||
- GitHub Cloud connections must use a fixed API base URL instead of asking the user for an instance URL.
|
||||
- Connection verification must confirm repository read access.
|
||||
- Authenticated user metadata from `GET /user` should be stored when available for display purposes.
|
||||
- Accessible repositories must be loaded from the authenticated user's GitHub repository list.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- A user can add, update, list, and remove a GitHub connection from settings.
|
||||
- A token that can read repositories is accepted.
|
||||
- A token that cannot read repositories is rejected with a clear validation error.
|
||||
- Repositories available through the GitHub connection appear as selectable repository sources in project settings.
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- OAuth browser login flows
|
||||
- GitHub App installation authorization
|
||||
- Background repository synchronization beyond on-demand fetches
|
||||
Reference in New Issue
Block a user