When doing a git rebase, I often have difficulty working out what is happening with the ‘local’ and ‘remote’ when resolving conflicts. I sometimes have the impression that they...
In Git I can do this: 1. Start working on new feature: $ git co -b newfeature-123 # (a local feature development branch) do a few commits (M, N,...
Suppose you have a history containing the three commits A, B and C: A-B-C I would like to combine the two commits A and B to one commit AB:...
I’d like to rebase to a specific commit, not to a HEAD of the other branch: A --- B --- C master \ \-- D topic to A ---...
Take the following case: I have some work in a topic branch and now I’m ready to merge back to master: * eb3b733 3 [master] [origin/master] | * b62cae6...
I’ve asked before about how to squash the first two commits in a git repository. While the solutions are rather interesting and not really as mind-warping as some other...
I can’t really ever think of a time when I would use git merge rather than git rebase and not want to have a commit show up. Is there...
I have conflicting branches, feature_x branched from main. Let’s say when rebasing feature_x on current main, while resolving conflicts, I decide to take some (not all) of “their” (i.e....
I was working on a repository on my GitHub account and this is a problem I stumbled upon. Node.js project with a folder with a few npm packages installed...
I’m new to git and I’m trying to understand the difference between a squash and a rebase. As I understand it you perform a squash when doing a rebase....