/Git

This Is How I Git

- Daniel Stenberg tl;dr: "I have a very simple approach and way of working with git in curl. This is how it works."

featured in #215


A Survey Of Git Best Practices

- David Golden tl;dr: David researched articles around Git best practices for a work presentation and collated the most frequently practices, in this post.

featured in #204


SQL Queries For Git Repositories

tl;dr: "A command-line tool for running SQL queries on git repositories meant for ad-hoc querying of git repositories on disk through a common interface (SQL)."

featured in #199


Highlights From Git 2.28

- Taylor Blau tl;dr: "A new configuration option, init.defaultBranch is being introduced to replace the hard-coded term Master," and more.

featured in #196


Easily Rename Your Git Default Branch From Master To Main

- Scott Hanselman tl;dr: "Master-slave is an oppressive metaphor, it's inaccurate and can deter someone new getting excited about learning the technology. Post outlines how to make the change.

featured in #185


Highlights From Git 2.26

- Taylor Blau tl;dr: "With features and bug fixes from over 64 contributors, 12 of them new. Here’s our look at some of the most exciting features and changes introduced."

featured in #178


Git From The Inside Out

- Mary Rose Cook tl;dr: Mary's article focuses on "the graph structure that underpins Git and the way the properties of this graph dictate Git’s behavior."

featured in #165


How To Write A Commit Message

tl;dr: Guideline is "write a concise message, starting with a capitalized verb in the root form, explaining what you did to the code and what the code does to the software."

featured in #161


Highlights From Git 2.24

- Taylor Blau tl;dr: With features and bug fixes from over 78 contributors, 21 of them new. A look at some of the most exciting features and changes introduced since Git 2.23

featured in #160


How To Write Useful Commit Messages (My Commit Message Template)

- Jacob Herrington tl;dr: A good message should be able to allow the readers to understand (1) what was done at a glance (2) why the change was necessary (3) the details about what was done (4) any useful details concerning the change. You can see the template here.

featured in #156