30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# 05 GitHub Ticket Pull Request Visibility
|
|
|
|
## Goal
|
|
|
|
Show GitHub pull requests related to a ticket alongside the matching branches in the ticket detail view.
|
|
|
|
## Requirements
|
|
|
|
- Add a GitHub pull requests section to the ticket detail view using the existing provider-neutral pull request presentation model.
|
|
- Pull requests must be associated to a ticket using the same ticket-key-based branch naming convention as branch discovery.
|
|
- Show enough pull request information to identify and open the matching item, at minimum:
|
|
- title
|
|
- provider identifier or number
|
|
- repository source
|
|
- status if available
|
|
- The implementation may derive pull request matches from source branch names.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- A ticket shows GitHub pull requests whose source branch starts with the ticket key.
|
|
- Pull requests unrelated to the ticket key are not shown.
|
|
- The ticket detail view clearly separates branch matches from pull request matches.
|
|
- Pull request visibility remains compatible with mixed-provider repository connections.
|
|
|
|
## Out of Scope
|
|
|
|
- Pull request review actions inside KanbanGit
|
|
- Merge controls
|
|
- Status checks and CI reporting
|