Skip to content

Conversation

wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Aug 15, 2025

Once we snap for RC1, the RC1/RC2 branches should auto-merge to release/10.0, which should auto-merge to main. Will revert this once RC2 locks down.

@Copilot Copilot AI review requested due to automatic review settings August 15, 2025 16:16
@github-actions github-actions bot added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Aug 15, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR configures automated merge flows between branches for the .NET 10.0 release cycle. It sets up a hierarchical merge flow where RC branches merge to the release branch, which then merges to main.

  • Adds automated merge configurations for release/10.0-rc1, release/10.0-rc2, and release/10.0 branches
  • Establishes merge hierarchy: RC branches → release/10.0 → main
  • Uses quiet comments for all automated merge operations

@wtgodbe wtgodbe merged commit 0a62bbf into main Aug 15, 2025
7 of 30 checks passed
@wtgodbe wtgodbe deleted the wtgodbe/10merge branch August 15, 2025 16:20
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-rc1 milestone Aug 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant