Git Commands That Cover 90% of a Developer's Daily Workflow (jsdev.space)

Screenshot of jsdev.space: Git Commands That Cover 90% of a Developer's Daily Workflow

First screen, captured 1 year ago.

Looks similar

Screenshot of lalitm.com: The git history command

The git history command (lalitm.com)

409 points by turbocon 3 months ago | 287 comments

Lalit Maganti's essay arguing that git's experimental history command (reword, split, fixup) deserves more attention as a lighter alternative to jj.

git git-history jj version-control

Screenshot of github.blog: CLI tricks every developer should know

CLI tricks every developer should know (github.blog)

29 points by kiyanwang 3 years ago | 20 comments

Screenshot of blog.gitbutler.com: How core Git developers configure Git

How core Git developers configure Git (blog.gitbutler.com)

253 points by chmaynard 1 year ago | 41 comments

How Core Git Developers Configure Git (blog.gitbutler.com)

418 points by lnkl 1 year ago | 90 comments

GitButler blog post by Scott Chacon describing git config settings that core Git developers change and that arguably should be defaults.

git git-config version-control gitbutler

Screenshot of jsonjoy.com: CRDT Benchmarks

CRDT Benchmarks (jsonjoy.com)

154 points by streamich 3 years ago | 39 comments

Screenshot of piechowski.io: Git commands I run before reading any code

Git commands I run before reading any code (piechowski.io)

2140 points by grepsedawk 6 months ago | 459 comments

Blog post by Ally Piechowski describing five git commands to find churn hotspots, bus factor, bug clusters, and crisis patterns before reading a codebase.

git code-review codebase-analysis version-control

Looks similar

The git history command(lalitm.com)

CLI tricks every developer should know(github.blog)

How core Git developers configure Git(blog.gitbutler.com)

How Core Git Developers Configure Git(blog.gitbutler.com)

CRDT Benchmarks(jsonjoy.com)

Git commands I run before reading any code(piechowski.io)