Merged
Conversation
The intent of this is that codeowners in release/dnup does not notify others about code changes, such that the code flow from `main` to `release/dnup` doesn't trigger the pings. The codeowners file is meant to inform others about the SDK, but dnup is a separate product that others don't need to be notified about - the code change would've already made it to main in the SDK, so they've already been notified This assumes that the codeowners file in the branch is respected by github over the one defined by `main`, which is what the docs suggest: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the merge-flow configuration so that merges from main into release/dnup keep the target branch’s CODEOWNERS file, preventing CODEOWNERS changes from being propagated (and therefore avoiding unintended reviewer pings) when syncing SDK changes into the dnup release branch.
Changes:
- Add
CODEOWNERSto theResetToTargetPathslist for themain→release/dnupmerge-flow configuration.
MiYanni
approved these changes
Feb 25, 2026
Member
Author
|
/ba-g no checks are running as no sdk source code was changed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The intent of this is that codeowners in release/dnup does not notify others about code changes, such that the code flow from
maintorelease/dnupdoesn't trigger the pings. The codeowners file is meant to inform others about the SDK, but dnup is a separate product that others don't need to be notified about - the code change would've already made it to main in the SDK, so they've already been notifiedThis assumes that the codeowners file in the branch is respected by github over the one defined by
main, which is what the docs suggest: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners