Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
What are the benefits of starting a Git repo with an empty commit?
Found an article about starting a repo with an empty commit. Read the post a couple of times, but still don't understand the reasoning:
git logand other commands blow up with terrifying error messages.
2. You can’t
git resetback to that initial state.
Based on the first 2 section titles above I suspected that this may be a satirical writing.
3. You can’t rebase the initial commit.
This however seems like a valid point (echoed by a linked article, Lesser Known Git Commands, found in the original post), but when I start thinking about it, I just can't see how this is useful in practice (or what it tries to prevent).
Linked in the original post: (2008?) Git Magic - Appendix A. Git Shortcomings: Initial Commit
I agree with the "counting from 0" sentiment, but still don't get what would be the benefits of an empty initial commit, other than being pedantic.
Linked in the original post: (2010) How I initialize my Git repositories | Kevin Deldycke
This post does give a rationale for using this trick for code archeology purposes (still don't get the specifics, but I understand that this is for a special use case).
Links in items 3. and 4. are obviously dated and this whole idea obviously never took off(?), but I'm still wondering if there is still a benefit to it - or the changes in Git since then obviate its necessity.
Of course, after typing all this did I find the SO threads:
Both have the main theme of "How to rebase the whole history, including the first commit?".