27 lines
1.3 KiB
Markdown
27 lines
1.3 KiB
Markdown
# 04 GitHub Ticket Branch Discovery by Ticket Key
|
|
|
|
## Goal
|
|
|
|
Show GitHub branches related to a ticket by matching configured repository branches against the ticket key prefix.
|
|
|
|
## Requirements
|
|
|
|
- Add GitHub branch matches to the ticket detail view through the same provider-neutral branch section used for other providers.
|
|
- For each configured GitHub repository connection, identify branches whose names start with the ticket key.
|
|
- A matching branch must be shown on the ticket when its name starts with the exact ticket key, for example `AUTH-42-...`.
|
|
- Present matches in a way that makes the repository source and provider clear.
|
|
- The first implementation may use direct fetches or a simple cache, but it must not require a large background sync system.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- A ticket with key `AUTH-42` shows GitHub branches such as `AUTH-42-login-form`.
|
|
- Branches that do not start with the ticket key are not shown.
|
|
- If multiple configured repositories contain matching branches, the ticket shows matches from each relevant repository.
|
|
- The branch section remains compatible with mixed-provider repository connections.
|
|
|
|
## Out of Scope
|
|
|
|
- Commit listing
|
|
- Branch creation from inside KanbanGit
|
|
- Cross-ticket branch disambiguation beyond exact ticket-key prefix matching
|