This is the second time I come back to this video. You saved me again, I almost had another heart attack! I must get better at this for my heart's sake xD
Great video!!. Just a note for newbies like me, @1:30 "Accessibility bug fix" is not the latest commit. @2:11 Jack is sqaushing the newer/latest commits (Number 2 & 3) into an older commit "Accessibility bug fix" (Number 1).
your work is cleaner and concise and actually practical and related to work. thanks for creating practical tuts. hoping to see some more stuuff from you. peace out.
Never used git squash. heard about it. you make it so simple. always thought how can I combine my commits. and here it is "git squash". splendid short clip on "git squash" that made my life much easier. GRATITUDE !!!!!!!!!!!!!!!!!!!!!!!! Mathew. K from Colorado
Just a tip about all your videos: when trying to help people with vim, saying 'ESC : W Q' and printing these uppercase characters on screen could confuse some people as it is necessary that they are lowercase!
Mate you are spot on the topic! so many other tutorial on your tube make confuse with other stuff! I liked the way you explained! I know now how to Squash! Thank you
I was a dev for over a decade. And it's only now that I'm a software manager that I actually had to learn how to squash my commits. LOL Thanks for the tutorial.
Yeah. If your squashing a lot of tiny commits that are part of a larger feature you can generally get away with summarizing them all with a single commit message.
Thanks a lot, that was exactly what i need. I do desktop apps (with native GUI frameworks) and need to always test on all platforms and i'm using git as a file sync tool, so i have lots of commits.in my branch just for that purpose. Now i need a to write a little script that will automatically squash all empty commit messages into the last one with a message. Nice.
Thanks you for explaining each and every step and not just assuming I know how to use vim like other tutorials seem to do. Even though I do, it really helps to be able to follow exactly what you are doing.
Thanks to your feedback on this video and my rebasing video (ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-f1wnYdLEpgI.html ), I created another video in the same style that goes in depth about other ways you can manipulate git history - including amending, rewording, deleting, reordering and splitting commits - ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ElRzTuYln0M.html. Check it out if you enjoyed this video, I think you'll find a lot of value there!
just found out your channel, i love these clear and objective explanations. +1 this week i dealt with some uncomfortable situation , i just pushed a branch that i created whose original parent was a wrong branch, and it went with all the wrong's branch commit history and i didn't knew how to solve that, what would you do?
Nice video and well explained. You could have showed us the output of "git log" before and after the operation, but your visualizations do the same job so it's cool. Are the separate commits recoverable after the squash operation or are they lost forever?
That's a good suggestion. I should have shown both the logs side-by-side. As for recovering commits after squashing, it is possible by using Git's reference logs. I'm not familiar with the process but this article might help: www.atlassian.com/git/tutorials/rewriting-history/git-reflog
Thank you, this helped me. I didn't know what I was supposed to do when updating the commit message, I was thinking of deleting everything included the commented out lines, but you showed me that there was no need, once you save with the new message, git throws out anything with a # in front.
What he did in this video can be achieved by using "fixup" instead of "squash", it's like squash, but discards the commit messages of the squashed commits :D