Repository navigation
.NET: Python: Document that Python and .NET changes go in separate PRs #9170
Description
Description
Reviewers have asked that Python and .NET changes not be combined in a single pull request, because cross-language PRs are much harder to review (see the review feedback on #8993). That expectation isn't written down anywhere today. The only hint is the Python: / .NET: title-prefix convention, so contributors keep opening mixed PRs.
Expected behavior: CONTRIBUTING.md states that each PR covers one language. Changes under python/ and dotnet/ go in separate PRs with the matching title prefix, and when the same feature lands in both languages the two PRs link to each other.
Alternatives considered: relying on reviewers to ask for a split each time. That costs a review round-trip and means closing and reopening PRs, as happened with #8993, #8994, and #8995.
Language/SDK
Other / Not Applicable
Activity
[-]Document that Python and .NET changes go in separate PRs[/-][+]Python: Document that Python and .NET changes go in separate PRs[/+][-]Python: Document that Python and .NET changes go in separate PRs[/-][+].NET: Python: Document that Python and .NET changes go in separate PRs[/+]marklicata commentedon Oct 7, 2026
A separate issue tracking this change isn't needed. This update will be folded into other work the core team is doing.