Skip to content

Conversation

@nagilson
Copy link
Member

@nagilson nagilson commented Oct 24, 2025

I think this is a good idea since we need to ship out of release/dnup. This would allow us to work in the dnup branch while reducing effort needed to sync the release branch backup, and also allowing us to hotfix an existing release without including any other recent changes. Then the code gets mirrored to internal for the actual build.

This is different than some of the other branch workflows since dnup only has one supported version at a time.

I think this is a good idea since we need to ship out of release/dnup. This would allow us to work in the `dnup` branch while reducing effort needed to sync the release branch backup, and also allowing us to hotfix an existing release without including any other recent changes.

This is different than some of the other branch workflows since dnup only has one supported version at a time.
Copilot AI review requested due to automatic review settings October 24, 2025 21:11
Copy link
Contributor

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 adds automation for merging changes from the dnup branch to release/dnup, streamlining the release workflow by reducing manual synchronization effort and enabling isolated hotfixes without including recent dnup changes.

Key Changes:

  • Adds a new merge flow configuration entry for the dnup branch to automatically merge into release/dnup

@nagilson nagilson requested a review from a team October 24, 2025 21:11
@nagilson nagilson enabled auto-merge October 24, 2025 21:12
@marcpopMSFT
Copy link
Member

I don't know if we need separate branches until we start servicing but there is no harm in having this flow.

@nagilson nagilson disabled auto-merge October 28, 2025 22:18
@nagilson nagilson merged commit c401b59 into main Oct 28, 2025
4 of 6 checks passed
@nagilson nagilson deleted the dnup-release-flow branch October 28, 2025 22:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants