I think this happens because github is not stack aware so the child pr has the changes from the parent pr so github automatically adds the codeowners for both changes. We're working on better support for this with our own versioning system that is stack aware and can handle this better!
s
Scott Richardson
04/05/2023, 11:04 PM
ack thanks for the response!
n
Nikolaus
04/06/2023, 9:16 PM
In the GitHub UI it's possible to set the PR base as you create the PR to avoid this issue, because GitHub only looks at the changes from the PR base when finding Code Owners. (Draft PRs also don't have Code Owners added, so you can make a draft PR and then fix the base before setting it ready for review)