4.3.5 Guidelines for contributions

Prefer small atomic commits over large ones that do many things.

Do not mix refactoring and new features.

Do not mix style changes, for example indentation changes, with actual code changes.

If you add new messages to a *.proto file, add appropriate documentation as well.

Run the unit tests for comment compliance to check if you followed the correct syntax guidelines for *.proto files.

Follow the guidelines for commit messages.

Sign off commit messages.

Name branches meaningfully and consistently.

If a commit contains work-in-progress, add the WIP label to the commit message.

Section 4.3.4, "Guidelines for writing commit messages"

Section 4.3.6, "Interface conventions"

Section 4.3.9, "Commenting on messages"

Section 4.3.10, "Commenting on fields and enums"

Section 4.3.3, "Signing off commits"