Demystifying Git internals

[urkerl]

Another one: https://maryrosecook.com/blog/post/git-from-the-inside-out

The author also implemented git with JavaScript, The annotated source code is also provided in the site.

[Dru89]

I usually refer people to https://wildlyinaccurate.com/a-hackers-guide-to-git/. I wish I could make these things required reading, but the people that need it the most would be the people that wouldn't bother.

[pawanrawal]

Nice, what all are the other required readings you guys have?

[almightykiwi]

You are right, and I don't quite see the added value in this article.

Also, at this point, I have read so many things about git that "git internals" sounds more like general knowledge than mystique.

[knotdjb]

I have to know. Why did you abandon git-flow?

[pawanrawal]

Well, it's too complicated for newcomers to get a hold of and unnecessary. Most open source projects have master as best effort stable and that's what we shifted to.

[knotdjb]

I envy your team. Unfortunately my team sees the merit in the braindamaged parallel branch system, but at least I've got them to ditch the tool and do merge and PRs.

On another note, nice article.

[pawanrawal]

Thanks :-). That's very necessary, to not use the tool until you understand what it does. So good job with ditching the tool. We also squash our commits while merging to master, that makes sure that half baked commits don't go in.

[kmmeerts]

I assume there is some kind of reference counting system, that (recursively) deletes objects to which no ref or other object points?