Seventeen years ago, the Linux community embraced Git as its universal open source version control solution. Created by Linus Torvalds, Git replaced BitKeeper, a proprietary but free-of-charge option that worked, to a point, until it didn’t (and ultimately started costing a fee).
In the years since, there’s been little to no agreement on what the term “Git” actually means but there’s no disputing its rockstar status in the DevOps world. Tens of millions developers rely on Git’s fast and seamless branching capabilities every single day. In fact, 85% of DevOps professionals who took our 2021 Global DevSecOps Survey said they use Git for source control.
So, to honor this anniversary, we share our favorite Git tips and tricks and look back at the origins of its name, its 15th anniversary celebration, and even a declaration from one of our own who was certain Git would never be in his toolkit. No, really.
The origin of the name Git
There’s not much quirky or charming about the world of DevOps, but the theories around the origin of the name Git may be an exception. Torvalds claimed to have named Linux after himself, and he said Git (British slang for “jerk”) was no different. “I’m an egotistical b*stard, and I name all my projects after myself,” he said at the time.
The source code’s README takes the story in a different direction: Git is easy to pronounce, not used by UNIX, and could sound like “get.” It could be British shade-throwing, or it could stand for “global information tracker” (the choice of those happily working with a functioning tool). And for those frustrated with Git, there’s also “goddamn idiotic truckload of sh*t.”
Tips and tricks for better Git
Is it possible to improve on a tool that so many use every single day? Actually, it is, starting with 15 ways to get a better Git workflow. Learn how to:
- autocomplete commands
- use Git blame more efficiently
- reset files
- understand the plugins
Also, Git can help keep merge requests tidy and humming along.
For an exhaustive look at how GitLab uses Git internally, including .gitconfig on steroids, the lowdown on aliases, and command line tips, we’ve gathered a life-changing list. Also, here’s our take on why (and how) to keep your Git history clean and how to do it using interactive rebase.
Remembering the 15th anniversary celebrations
Landmark anniversaries always make people reflect, and Git’s 15th in 2020 was no exception. Not only was there an actual party – Git Merge 2020, our staff developer evangelist Brendan O’Leary admitted the unthinkable: Back in the day, he was never ever going to use Git. Brendan, who obviously has learned his lesson, also teamed up with GitHub’s distinguished software engineer Jeff King to talk about Git’s impact on software development.
Although there’s a lot to learn about Git, Brendan and other developers consistently stress the simplicity is what sets it apart. So here are three of our most bookmarked pages of straightforward Git advice:
So make sure to raise a glass to 17 years of Git and its many benefits.