You know atomic commits are the way to go, but you struggle making them happen with Git. Nathan shares a simple, step-by-step way to create atomic commits in the command line.

Yesterday a co-worker showed me a neat trick that I was previously unaware of. I’d been looking for something like it for some time, and I…

How hackers start their afternoon. HackerNoon is a free platform with 25k+ contributing writers. 100M+ humans have visited HackerNoon to learn about technology

The fact that Microsoft is buying GitHub has left a lot of developers with a deep feeling of unease and a lot of them are now looking for alternatives. One of those is GitLab and that company has decided to strike the iron while it’s hot. To attract even…

A curated list of six awesome open source Github alternatives that you can host on your own server.

Helping millions of developers easily build, test, manage, and scale applications of any size – faster than ever before.

Flight rules for git. Contribute to k88hudson/git-flight-rules development by creating an account on GitHub.

Do you use past or imperative tense commit messages?

A guide to understand the importance of commit messages and how to write them well - RomuloOliveira/commit-messages-guide

If like me you're using Git for multiple client projects and open source work on
GitHub on the same machine, you'll hit a problem early on where the email
address you use for GitHub is different to the email address you need to use for
client projects.

Why…

I like Git commit messages. Used well, I think they’re one of the most powerful tools available to document a codebase over its lifetime. I’d like to illustrate that by showing you my favourite ever Git commit.

Switching branches and restoring files to its initial state are very common operations. Why the hell should we use a single command to perform such different actions?

A long-standing objection to making bulk changes to code using automated tools (e.g. to conform to a given code style) is that it clutters the output of git blame. With git 2.23, this does not have to be the case anymore! In this post I will start by explaining…

Learn why Git flow complicates the lifecycle and discover an alternative to streamline development.

The open source Git project just released Git 2.28 with features and bug fixes from over 58 contributors, 13 of them new. We last caught up with you on the latest in Git back when

Git has a reputation for being confusing. Users stumble over terminology and phrasing that misguides their expectations. This is most apparent in commands that “rewrite history” such as git cherry-pick or git rebase. In my experience,…

Compare git rebase with the related git merge command and identify all of the potential opportunities to incorporate rebasing into the typical Git workflow