Addons: copy project overrides when copying addon settings#959
Open
dallasnetprofu02-design wants to merge 1 commit into
Open
Conversation
Author
|
@martastain this is ready for review when you have a chance. I kept the change focused on the legacy manual-copy path: copy into the target variant's addon version instead of the source version, and add an explicit flag to include project overrides when copying an individual addon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of changes
Fixes the manual addon-settings copy flow so it migrates into the target variant's addon version and can optionally include project overrides.
Technical details
Closes #533