Skip to content

Use union merge strategy for release notes to avoid conflicts#19420

Open
T-Gro wants to merge 1 commit intomainfrom
eng/union-merge-release-notes
Open

Use union merge strategy for release notes to avoid conflicts#19420
T-Gro wants to merge 1 commit intomainfrom
eng/union-merge-release-notes

Conversation

@T-Gro
Copy link
Member

@T-Gro T-Gro commented Mar 10, 2026

Release notes files are append-only unordered lists where each PR adds one entry. With the default merge strategy, concurrent PRs that both append under the same heading (e.g. ### Fixed) produce merge conflicts even though order doesn't matter.

The union merge driver keeps both sides, eliminating these spurious conflicts. This is consistent with the existing use of merge=union for .sln and project files in this repo.

Release notes files are append-only unordered lists where each PR adds
one entry. With the default merge strategy, concurrent PRs that both
append under the same heading (e.g. ### Fixed) produce merge conflicts
even though order doesn't matter.

The union merge driver keeps both sides, eliminating these conflicts.
This is consistent with the existing use of merge=union for .sln and
project files in this repo.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Contributor

✅ No release notes required

@github-project-automation github-project-automation bot moved this from New to In Progress in F# Compiler and Tooling Mar 12, 2026
@T-Gro T-Gro requested a review from abonie March 13, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

2 participants