Merge conflicts can show up when you do a ‘git-merge’ or a ‘git-rebase’:
One way you can “anticipate” a git merge is with the ‘diff’ command
Here’s some bash pseudo code using command substitution:
diff -y <(git show branchA:file.txt) <(git show branchB:file.txt)
Remember though ☝️
A diff will always yield results, that’s what a patch is..
The key is when the SAME LINES are being changed: That’s the conflict! 😉
If the lines from diff don’t overlap…you can probably assume the merge or rebase won’t produce a conflict
(at least, for the file you looked at😊)
Here I break down how to read and set Linux permissions in numeric and symbolic mode: ⬇️
I wrote a script to automate the creation of two divergent git branches…’main’ and ‘feature’.
When I rebased ‘feature’ onto ‘main’..no worked was “saved”.
The following code:
git checkout feature
git rebase main -i
even show ‘noop’ in the text editor.
Turns out, my code was creating duplicate patches on each divergent branch (here’s how to reproduce it if your interested, github link)
So when I rebased, git skips “already introduced patches”.
My reaction after 2 hours of reaching this finding:
Here’s how I visualize a Git *Fast Forward* Merge:
Part 2 takes what was introduced in Part 1 and expands upon it.
I’ll show you how to create your own crontab file and some advanced syntax.
In Part 1 of this video, I’ll show you how to NEVER FORGET the format of a crontab file and how to read one:
System-Wide Crontab File
Man Page crontab(5)
How To Read ANY COLUMN
This simple and effective introduction to VIM will help you see the big picture and avoid a lot of the common snags people new to VIM get caught by.