Skip to content

docs: require one component per pull request #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RohanAdwankar merged 1 commit into from
Nov 2, 2026
Merged

docs: require one component per pull request #91

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@ Open an issue before substantial implementation work so maintainers can confirm

## Code Contributions

### Pull request scope

Each pull request must contain one independently reviewable component: a single feature, bug fix, refactor, or documentation change. Split work involving multiple features or separable components into individual pull requests, even when they support the same larger goal. Separate commits within one pull request do not replace separate pull requests.

Keep the implementation, tests, and documentation needed for that component together. If a component depends on another pull request, link the dependency and describe the review and merge order. Maintainers will ask for bundled changes to be split before review.

1. Fork the repository and create a focused branch from `main`.
2. Keep changes minimal and include documentation for user-visible behavior.
3. Validate the Helm chart:
Expand Down
Loading