Part 8 of 13 · 1 min read
How to build it so it holds up
- One concern per pull request; split formatting, renames and features.
- Add a test that fails before and passes after, and say so in the description.
- Link the issue and state why the change is needed.
- Keep the diff free of debug output, unrelated edits and secrets.
- Follow the project's style and tooling (formatter, linter, commit format, sign-off).
- Write an imperative commit subject under about 72 characters, with a body for the why.
- Document new public behaviour where the project documents things.
- Disclose AI assistance when the project asks, and review every line yourself.
- Be patient and polite; review can take days.