docs(CONTRIBUTING): add guideline to separate cosmetics from function…

[fishman]

…al commits

Inspired by FFmpeg code-review practices, this rule keeps diffs reviewable by requiring cosmetic changes to be in their own commits.

What type of PR is this?

/kind documentation

What this PR does / why we need it:

In general this is good practice, but beyond that it catches a lot of cases where AI generated code edits and beautifies comments.

Summary by CodeRabbit

• Documentation
  • Updated contributor guidance for code reviews.
  • Added advice to keep cosmetic changes separate from functional changes, and to split mixed work into separate commits or pull requests when helpful for review.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d132ae48-86fa-4f91-9162-e3c8ab62bbeb

📥 Commits

Reviewing files that changed from the base of the PR and between 3b466ff and 5ab6c22.

📒 Files selected for processing (1)

• CONTRIBUTING.md

---

📝 Walkthrough

Walkthrough

A single documentation line was added to CONTRIBUTING.md's Code Review section, advising contributors to separate cosmetic changes from functional logic changes and to split them into separate commits or PRs.

Changes

Documentation update

Layer / File(s)	Summary
Code Review guidance addition CONTRIBUTING.md	Added a bullet advising contributors to avoid mixing cosmetic-only changes with functional changes, splitting cosmetics into separate commits/PRs when appropriate.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A single line, so small and neat,
Keeps cosmetic and logic changes discreet.
Split your commits, hop by hop,
Reviewers rejoice—the diffs won't flop!
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the CONTRIBUTING docs update adding a guideline to separate cosmetic changes from functional work.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch pr-commit-rules

---

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Code Review

This pull request updates the CONTRIBUTING.md file to add a guideline advising contributors to separate cosmetic changes from functional changes to keep diffs reviewable. The feedback suggests a minor grammatical correction to ensure plural agreement in the newly added text.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[mesutoezdil]

/lgtm

[saiyam1814]

LGTM

[archlitchi]

/lgtm

[hami-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: archlitchi, fishman, saiyam1814

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [archlitchi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment