onex-merge-planner

To prioritize pull requests and minimize conflicts, the merge planner automates PR classification, scoring based on size, age, CI status, and review status, then determines a safe priority-ordered merge sequence.

Automating merge order for multiple concurrent pull requests involves classifying PRs by complexity, scoring them on conflict risk and CI status, and generating a priority-ordered sequence to ensure a smooth integration process.

Yes, you need the GitHub CLI to automate pull request merging, as the merge planner requires access to it to operate within the context of a repository managing multiple concurrent PRs.

PR classification handles dependency management and CI status by categorizing pull requests into types like Accelerator, Normal, or Blocked, using these factors to score priority and optimize the merge order.

Merging pull requests in the wrong order breaks CI because it can lead to unnecessary conflicts and broken integration, which the automated merge planner solves by optimizing the merge sequence based on conflict risk.

Yes, you can use an automated merge planner for a repository with multiple concurrent PRs, as it operates specifically within this context to classify, score, and sequence pull requests safely.