26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# PR Conflict Predictor
|
|
|
|
Predict likely merge conflicts before a pull request is ready to merge, so teams can rebase earlier and avoid last-minute integration pain.
|
|
|
|
## Problem
|
|
Large repos with many parallel branches often discover conflicts only at merge time, when context is cold and release pressure is high.
|
|
|
|
## Core capabilities
|
|
- Track active branches and PRs, including touched files and dependency graph impact.
|
|
- Compute a conflict risk score based on overlap, file churn, and branch age.
|
|
- Post proactive PR comments when risk crosses a threshold.
|
|
- Suggest mitigation steps: rebase now, split PR, or coordinate with specific authors.
|
|
|
|
## MVP scope
|
|
- Integrate with GitHub or Gitea API for open PR metadata.
|
|
- Build nightly and on-push risk analysis.
|
|
- Add a dashboard with high-risk PRs and conflicting file hotspots.
|
|
|
|
## Success criteria
|
|
- Fewer merge-blocking conflicts in release branches.
|
|
- Lower average time from review complete to merge.
|
|
|
|
## Stretch ideas
|
|
- Simulate merge outcomes in a temporary branch.
|
|
- Learn repo-specific risk patterns from historical conflict data.
|