summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorAdam T. Carpenter <atc@53hor.net>2023-04-15 08:49:04 -0400
committerAdam T. Carpenter <atc@53hor.net>2023-04-15 08:49:04 -0400
commita830f959ed0449032d1c67a68da3619b004333d8 (patch)
treebd582e533c93d07a0b56c16a60a77896e8904096 /posts
parent3a697e28ff94605b474179795d0eb364aee39287 (diff)
download53hor-a830f959ed0449032d1c67a68da3619b004333d8.tar.xz
53hor-a830f959ed0449032d1c67a68da3619b004333d8.zip
feat:: new youtube vids
Diffstat (limited to 'posts')
-rw-r--r--posts/2023-04-08-git-pull---rebase-why-you-might-want-to.php7
-rw-r--r--posts/2023-04-12-git-bisect-find-breaking-commits-easily.php7
2 files changed, 14 insertions, 0 deletions
diff --git a/posts/2023-04-08-git-pull---rebase-why-you-might-want-to.php b/posts/2023-04-08-git-pull---rebase-why-you-might-want-to.php
new file mode 100644
index 0000000..08be2d3
--- /dev/null
+++ b/posts/2023-04-08-git-pull---rebase-why-you-might-want-to.php
@@ -0,0 +1,7 @@
+<h1>Git pull --rebase? Why you might want to!</h1>
+
+<p class="description">
+ In a team of developers you may find rebasing when you pull changes to be more sensible than merging. This video explains the practical differences between merge pulling and rebase pulling in git so you can decide for yourself.
+</p>
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/GYlIwSpneXg" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
diff --git a/posts/2023-04-12-git-bisect-find-breaking-commits-easily.php b/posts/2023-04-12-git-bisect-find-breaking-commits-easily.php
new file mode 100644
index 0000000..9d76614
--- /dev/null
+++ b/posts/2023-04-12-git-bisect-find-breaking-commits-easily.php
@@ -0,0 +1,7 @@
+<h1>Git-bisect: Find Breaking Commits Easily</h1>
+
+<p class="description">
+ We'll use git-bisect to help search the commit history for a commit which introduced a bug. As a bonus, we'll look at using git-cherry-pick and git-revert to undo breaking changes once we've found them.
+</p>
+
+<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/MUukZIXGH9Y" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>