You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[no-ci] docs: clarify contributor coordination and issue readiness - #3103
An open issue can capture an investigation or tentative proposal before an implementation plan has been agreed. Make that distinction clear so contributors can coordinate useful work and avoid implementing approaches that maintainers are still evaluating.
Clarify when contributors should coordinate scope and validation with maintainers, while welcoming bug reports, evidence, and direct PRs for small standalone corrections.
Explain responsibility for agent-assisted contributions: provide relevant context, understand the complete diff, keep changes focused, and report actual validation and remaining gaps.
Align AGENTS.md with this guidance. Require prominent readiness notices for investigations and proposals awaiting agreement, distinguish them from routine bug reports and approved work, and update the notices when the direction changes.
Related: #3074, which illustrates the need to distinguish an investigation from implementation-ready work. The cache investigation remains open.
Validation
pre-commit run --files AGENTS.md CONTRIBUTING.md — passed.
pre-commit run --all-files — passed on the merged head, including link checking.
git diff --check main...HEAD — passed.
Checklist
Validation appropriate to this documentation-only change is complete; no runtime tests were added.
The documentation is up to date with these changes.
rwgk
changed the title
docs: clarify contributor coordination and issue readiness
[no-ci] docs: clarify contributor coordination and issue readiness
Oct 14, 2026
Reviewing files that changed from the base of the PR and between 9dc5f33 and c6a9bc5.
📒 Files selected for processing: 2
AGENTS.md
CONTRIBUTING.md
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.
📝 Summary
Summary by CodeRabbit
Documentation
Expanded contributor guidance for reporting issues, coordinating before larger or shared work, and identifying when approval is needed.
Clarified expectations for contribution scope, validation, review, and infrastructure access.
Added guidance for agent-assisted contributions, including reviewing changes and reporting validation gaps.
Added instructions for documenting readiness, approved work, and changes in implementation direction while excluding private information.
AGENTS.md and CONTRIBUTING.md add guidance for issue reporting, contribution coordination, issue readiness notices, shared infrastructure changes, and agent-assisted contributions.
Changes: Contribution Guidance
Layer / File(s)
Summary
Scope and reporting AGENTS.md, CONTRIBUTING.md
Adds issue-reporting details and guidance on coordinating scope, review, validation, and shared work with maintainers.
Issue readiness and infrastructure AGENTS.md, CONTRIBUTING.md
Adds guidance for distinguishing observed problems from proposals, setting and updating readiness notices, and coordinating changes to shared infrastructure.
Agent-assisted contributions CONTRIBUTING.md
Adds expectations for providing context, understanding the full diff, validating changes, reporting checks and gaps, and following agreed scope.
Suggested reviewers:mdboom
Priority: ⬇️ Low
Change: Other
Merge Risk:⚪ Minimal · up to c6a9b
The revised guidance distinguishes routine reporting from implementation approval, and permits explicitly requested reports without maintainer assignment. No actionable merge risk remains.
- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
This branch has not been deployed
No deployments
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
cuda.bindingsEverything related to the cuda.bindings modulecuda.coreEverything related to the cuda.core modulecuda.pathfinderEverything related to the cuda.pathfinder moduledocumentationImprovements or additions to documentation
1 participant
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.
rwgk
added
documentation
Description
An open issue can capture an investigation or tentative proposal before an implementation plan has been agreed. Make that distinction clear so contributors can coordinate useful work and avoid implementing approaches that maintainers are still evaluating.
AGENTS.mdwith this guidance. Require prominent readiness notices for investigations and proposals awaiting agreement, distinguish them from routine bug reports and approved work, and update the notices when the direction changes.Related: #3074, which illustrates the need to distinguish an investigation from implementation-ready work. The cache investigation remains open.
Validation
pre-commit run --files AGENTS.md CONTRIBUTING.md— passed.pre-commit run --all-files— passed on the merged head, including link checking.git diff --check main...HEAD— passed.Checklist