pr-merge-temporal

You can validate multiple pull requests together by merging them into a temporal integration branch. This staging branch runs builds and tests to check inter-PR dependencies and surface conflicts before affecting the base branch.

A temporal branch is a temporary integration branch created from the base branch tip. You need it to sequentially merge multiple PRs, handle conflicts in isolation, and ensure a clean base before final integration.

Merge order for multiple PRs is determined by resolving inter-PR dependencies or using explicit user input. The Skill enumerates PRs and sequentially merges them onto the temporal branch with conflict handling.

Yes, you can run builds and tests on a temporal staging branch without altering the main branch. The workflow creates a temporal branch, merges PRs sequentially, and reports validation results before any base branch update.

The best way to handle merge conflicts across multiple PRs is ordered merging on a temporal branch. This approach surfaces conflicts during sequential merges and applies conflict handling before the base branch is affected.

Merging fails when inter-PR dependencies are not validated because conflicting changes break the build. Creating a temporal branch to merge and validate PRs sequentially surfaces these conflicts before they affect the base branch.