Repository navigation
Document that Python and .NET changes go in separate PRs - #9168
Closed
Mark Licata (marklicata) wants to merge 1 commit into
Closed
Mark Licata (marklicata) wants to merge 1 commit into
Mark Licata (marklicata) wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mark Licata (marklicata)
temporarily deployed
to
github-app-auth
October 7, 2026 15:34 — with
GitHub Actions
Inactive
Mark Licata (marklicata)
temporarily deployed
to
github-app-auth
October 7, 2026 15:34 — with
GitHub Actions
Inactive
Mark Licata (marklicata)
temporarily deployed
to
github-app-auth
October 7, 2026 15:35 — with
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The documentation clearly and consistently captures the intended contribution policy.
0 open findings
What changed in this PR
Documents the policy that Python and .NET changes should use separate pull requests.
Changes:
- Adds the policy to the contribution guidelines.
- Updates the recommended PR workflow with language prefixes and cross-linking guidance.
| File | Description |
|---|---|
CONTRIBUTING.md |
Documents language-specific PR requirements. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Mark Licata (marklicata)
temporarily deployed
to
github-app-auth
October 7, 2026 15:38 — with
GitHub Actions
Inactive
Mark Licata (marklicata)
marked this pull request as ready for review
October 7, 2026 15:57
Mark Licata (marklicata)
requested review from
SergeyMenshykh,
Tao Chen (TaoChenOSU),
Vincent Biret (baywet),
Eduard van Valkenburg (eavanvalkenburg),
Giles Odigwe (giles17),
Jose Alvarez (jpalvarezl),
Evan Mattson (moonbox3),
Peter Ibekwe (peibekwe),
Roger Barreto (rogerbarreto),
sophia-ramsey and
westey (westey-m)
as code owners
October 7, 2026 15:57
Mark Licata (marklicata)
temporarily deployed
to
github-app-auth
October 7, 2026 15:57 — with
GitHub Actions
Inactive
Author
|
Per Eduard van Valkenburg (@eavanvalkenburg) this change isn't needed. This will be folded into other work the core team is doing. |
Author
|
Per Eduard van Valkenburg (@eavanvalkenburg) this change isn't needed. This will be folded into other work the core team is doing. |
This branch was previously deployed
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.
Motivation & Context
Reviewers have asked that Python and .NET changes not be combined in one pull request, because cross-language PRs are much harder to review. That expectation isn't written down anywhere today. The only hint is the
Python:/.NET:title-prefix convention. This documents it in the contribution guidelines.Description & Review Guide
What are the major changes?
CONTRIBUTING.md: don't combine Python and .NET changes in a single PRPython:/.NET:title prefix, and link the PR in the other languageWhat is the impact of these changes?
Documentation only.
What do you want reviewers to focus on?
Related Issue
Closes #9170
Contribution Checklist
🤖 Generated with Claude Code