Summary
When the fragment update process detects updates, it currently (or risks) bundling multiple fragment updates into a single pull request. This should instead open one PR per fragment.
Motivation
Bundling multiple fragment updates into one PR causes conflicts and messy history — changes from different fragments get interleaved, making review, revert, and merge harder than it needs to be.
Proposed Solution
For each fragment with a detected update, open a dedicated pull request containing only that fragment's changes.
Summary
When the fragment update process detects updates, it currently (or risks) bundling multiple fragment updates into a single pull request. This should instead open one PR per fragment.
Motivation
Bundling multiple fragment updates into one PR causes conflicts and messy history — changes from different fragments get interleaved, making review, revert, and merge harder than it needs to be.
Proposed Solution
For each fragment with a detected update, open a dedicated pull request containing only that fragment's changes.