Skip to content

Conversation

@Brocco
Copy link
Contributor

@Brocco Brocco commented Jan 26, 2021

This fixes #11337 to allow for merging of a tree with another when the the file already exists in the tree being merged into.

@google-cla google-cla bot added the cla: yes label Jan 26, 2021
@Brocco Brocco force-pushed the schematic-overwrite-fix branch 2 times, most recently from 694e312 to b10d482 Compare January 26, 2021 20:44
Copy link
Member

@clydin clydin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like at least one E2E test is failing as well.
node ./tests/legacy-cli/run_e2e.js ./tests/legacy-cli/e2e/tests/generate/component/component-duplicate.ts

@Brocco Brocco force-pushed the schematic-overwrite-fix branch 3 times, most recently from 0f39a57 to df6dd97 Compare January 26, 2021 23:07
@Brocco Brocco force-pushed the schematic-overwrite-fix branch 2 times, most recently from 8bf63b6 to 21f15fc Compare January 27, 2021 15:47
@clydin clydin added the target: patch This PR is targeted for the next patch release label Jan 27, 2021
This fixes angular#11337 to allow for merging of a tree with another when the the file already exists in the tree being merged into.
@Brocco Brocco force-pushed the schematic-overwrite-fix branch from 21f15fc to 39e584f Compare January 27, 2021 15:56
@clydin clydin added the action: merge The PR is ready for merge by the caretaker label Jan 27, 2021
@alan-agius4 alan-agius4 merged commit a179828 into angular:master Jan 28, 2021
@Brocco Brocco deleted the schematic-overwrite-fix branch January 28, 2021 16:44
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MergeStrategy seems to be completely broken (mergeWith failure)

3 participants