When applying multiple blueprints to the same project. Its a bit annoying that they all show up on the resynth branch by default. They end up overwriting each other while maintaining clearly broken links to the origin PR
Description
The basic idea in this solution is to segment out resynth branches by blueprint instance. This solution creates two flavors of resynth branches.
A branch on initial application of the blueprint. This is before the blueprint instance exists, so it goes onto an initial application branch
A branch for subsequent updates to the blueprint.
Testing
How was this change tested?
Additional context
Add any other context about the PR here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue
When applying multiple blueprints to the same project. Its a bit annoying that they all show up on the resynth branch by default. They end up overwriting each other while maintaining clearly broken links to the origin PR
Description
The basic idea in this solution is to segment out resynth branches by blueprint instance. This solution creates two flavors of resynth branches.
Testing
How was this change tested?
Additional context
Add any other context about the PR here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.