What do I hate about Git?

10 things I hate about Git

• Complex information model.
• Crazy command line syntax.
• Crappy documentation.
• Information model sprawl.
• Leaky abstraction.
• Power for the maintainer, at the expense of the contributor.
• Unsafe version control.
• Burden of VCS maintainance pushed to contributors.

Why Git is so bad?

Remember, Git was created to handle Linux development; most projects have a single relationship with the remote server. So, first, it’s an overkill to use, like shooting pigeons with a Cruise missile. Second, because of its power, it’s extremely complex and makes it really easy to shoot yourself in the foot.

Is Git good or bad?

However, even once pushed, your commits are not entirely safe. Deleting Git branches may make some commits unreachable, i.e. they no longer belong to the history of any branch. Such commits will be quickly deleted, which may lead to loss of work.

Why is Git so great?

One of the biggest advantages of Git is its branching capabilities. Unlike centralized version control systems, Git branches are cheap and easy to merge. This facilitates the feature branch workflow popular with many Git users. Feature branches provide an isolated environment for every change to your codebase.

Why is git so confusing?

Git is hard to learn because its developers gave up on making it easy. The Git command we all know and “love” today was originally intended to be a low-level layer that other, more user-friendly programs would use as a middleman.

Why is head detached git?

A detached HEAD occurs when you are viewing a single commit in the history of a Git repository. You’ll see a message whenever you enter into detached HEAD state informing you that you are no longer on a branch.

Why is head detached Git?

How do I stop being bisecting?

git bisect reset is how you stop bisecting. By default it will reset the HEAD to where it was before you started, although you can also use git bisect reset to go to that one instead.

Why is Git so confusing?

Is it harder to debug with git bisect?

In particular, this will make it harder to use Git bisect, arguably the most powerful debugging tool in the Git toolbox. As an example, consider the following feature branch. Let’s say we introduced a bug towards the end of the branch. You may not discover this bug until weeks after the branch was merged to master.

Should git history be linear or non-linear?

There are many magnificent tools that can analyse and visualise complex Git history, both GUI- and CLI-based. These graphs contain valuable information about what has happened and when it happened, and we gain nothing by linearising it. Git is made for, and encourages, non-linear history.

Is there a better way to rebase a git repository?

Another approach would be to have Git pause during every step of the rebase process, test for any bugs and fix them immediately before proceeding. This is a cumbersome and error-prone process, and the only reason for doing it would be to achieve a linear history. Is there a simpler and better way? There is; Git merge.