Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use git conflict markers when we cannot merge text #76099

Merged
merged 13 commits into from
Nov 26, 2024

Conversation

CyrusNajmabadi
Copy link
Member

Fixes #74366

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner November 26, 2024 15:39
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 26, 2024
@CyrusNajmabadi CyrusNajmabadi requested a review from genlu November 26, 2024 15:39
@CyrusNajmabadi
Copy link
Member Author

@genlu ptal

@CyrusNajmabadi
Copy link
Member Author

@ToddGrun ptal

afterString);
return $"""

/* {header}
Copy link
Contributor

Choose a reason for hiding this comment

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

/* {header}

Out of curiosity, why not use the git merge markers for the new/removed cases too?

Copy link
Contributor

@ToddGrun ToddGrun left a comment

Choose a reason for hiding this comment

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

:shipit:

@dibarbet dibarbet modified the milestones: Next, 17.13 P3 Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead VSCode
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Unmerged changes" should use merge markers to mark refactoring conflicts across multiple targets
3 participants