Comment

Comment by uwemaurer

To me it is most important that the commit is focused only on one thing, and not mix any unrelated changes together.

We develop a Rust based tool HighFlux [1] which simplifies/automates working with git. In this workflow you create a feature branch for every feature you work on and it automatically commits all changes to this branch. After code review the branch gets merged as a squashed merge to have it in a single commit in the history.

1: https://www.highflux.io/

parent uwemaurer 4 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton