Thanks for your input, Nidhi! Yeah git is very powerful for crafting patches. I commit often and I use `git commit --amend` often (and in other projects I keep most all temporary commits around so I can retrace my steps later). Note that while you're working on a branch feel free to make as many commits as you want, just squash it before you mark your PR ready for review. And yeah, once we settle some rules/tips we can document them.
On Mon, Feb 2, 2026 at 11:02 AM Nidhi Bhawari <[email protected]> wrote: > Hi everyone, > As a new contributor, I agree that documenting this decision in > CONTRIBUTING.md would be very helpful. > > I recently learned to use `git commit --amend` to keep my PR history > clean. If the community decides to stick to the "one commit" rule, having > clear examples in the documentation on how to use "Trailers" (like > Co-authored-by: or Tested-by:) would be great. This way, new contributors > like me can ensure we keep the history clean while still giving proper > credit to reviewers and testers. > > Regards, > Nidhi >
