A look how branches work in Git

• git-branchless

  55 3,308 9.4 Rust

  High-velocity, monorepo-scale workflow for Git

The article talks about how branches are used for experimentation, but my opinion is that branches are actually often too heavyweight in Git – they're not convenient to use for local prototyping. I made the branchless workflow to improve on this use-case: https://github.com/arxanas/git-branchless

• gitjk

  1 826 0.0 JavaScript

  Undo what you just did in git

I watched your demo video and I don't see any advantages over using named branches, and you describe no specific advantages in your README.

You just didn't give your branch a name, and referred to commits by ID. Fine, I guess, but are names so bad that you're gonna adopt a non-standard git workflow?

`git undo` is cool. There have been a number of fun variations on it over the years, and yours seems fine, but it's usually a leaky abstraction. I expect that yours is, too, but that's just because git itself is a leaky abstraction; it's just really hard to build a strong foundation on sand.

https://github.com/mapmeld/gitjk

• 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.

  

• git-extras

  16 16,717 7.7 Shell

  GIT utilities -- repo summary, repl, changelog population, author commit percentages and more

• git-undo

  1 1 0.0 Awk

  Undo what you just did in git

Suggest a related project