Group changes into commits and rebase to build a better Git history

• gitplay

  2 20 8.6 TypeScript

  Learn how a software project (using git) evolved over time from its commit log. Its like YouTube for a git project. Desktop app built with Rust and SolidJS

You can read the markdown version [here](https://github.com/brainless/gitplay/issues/5)

## Problem statement

We all have worked on a feature intensively and had to refractor a lot of the code base (in early projects). But can't spend the mental expense to context switch from `writing code` to `make meaningful commit messages`.

A good commit history is at the expense of the developer, which results in breaking the "flow". As pg mentioned in his blog post [Holding a program in one's head][1], it be better to work in long stretches to have better developer productivity. And it is very common for devs to have to make code cleanups which are unrelated to the feature they are working on ([example tweet][2])

* Commit small and commit often

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project