what are the odds ?! i just searched for a git rebase video and the video you uploaded about 5 years ago was the first result i saw. really loved the video btw; decided to checkout your other videos and then boom, a video about git rebase is the most recent!
Thanks for taking the time to check out my other stuff! I can definitively say my newer videos are leaps and bounds higher quality than my older stuff, and I’m really trying to bring awareness to that, so I appreciate you checking it out!
When you say "keep your feature branch intact for documentation purposes" what do you mean does your local feature branch somehow gets deleted when a fast-forward happens? timestamp 3:10
The feature branch doesn't get deleted during a FF, but because rebase erases the fork feature branches fork from the main branch, you can't tell where the feature branch started.
If there are upstaged changes in the working directory then rebase will fail and you'll need to either stash or commit those changes to continue rebasing.
Rebasing a branch that is shared by other contributors is the pitfall. If someone else has your feature_branch pulled into their local workspace then rebasing it will cause issues for them. Since rebase works by erasing then re-creating commits, you can cause yourself and your teammates synchronization problems by rebasing shared branches/commits.
MORE GIT VIDEOS: ua-cam.com/play/PLfU9XN7w4tFwKwh_xPSQ_X1-hROQEpHnM.html
The best git animation on youtube. Helps me to visualise what is happening. Looking forward to the next one.
Appreciate it, and thanks for following my vids!
Nice cliffhanger! I'm excited to learn what happens next!
2:14 Subscribed. Thank you for the videos and esp. the animations: they are fantastic.
Wow, appreciate that!
what are the odds ?!
i just searched for a git rebase video and the video you uploaded about 5 years ago was the first result i saw.
really loved the video btw; decided to checkout your other videos and then boom, a video about git rebase is the most recent!
Thanks for taking the time to check out my other stuff! I can definitively say my newer videos are leaps and bounds higher quality than my older stuff, and I’m really trying to bring awareness to that, so I appreciate you checking it out!
When you say "keep your feature branch intact for documentation purposes" what do you mean does your local feature branch somehow gets deleted when a fast-forward happens? timestamp 3:10
The feature branch doesn't get deleted during a FF, but because rebase erases the fork feature branches fork from the main branch, you can't tell where the feature branch started.
At 2:52 we've already done git rebase main while on the feature_branch ?
Yeah, that would be one scenario. The other scenario could be that no other changes were pushed to main while the feature branch was in development
really good content
What is there are unstaged files in the feature branch ? Is the rebase update that file, but the files are not committed, then ?
If there are upstaged changes in the working directory then rebase will fail and you'll need to either stash or commit those changes to continue rebasing.
really nice video!
Thanks!
Awesome video! Thanks
Amazing Zack :)
I don't get it. What if one of the files you're changing has been updated by someone else? How does rebase work there?
You’ll get a conflict (just like you would during a merge) and you’ll need to tell Git how to incorporate the other person’s changes
Definitely earned that sub, great video and succinct explanation ;)
Thanks for the sub!
thank you
gooog
The second video in the series is marked PRIVATE
Is that on purpose?
Do you have more details?
I don't think I saw a pitfall here - what did I miss?
Rebasing a branch that is shared by other contributors is the pitfall. If someone else has your feature_branch pulled into their local workspace then rebasing it will cause issues for them. Since rebase works by erasing then re-creating commits, you can cause yourself and your teammates synchronization problems by rebasing shared branches/commits.
@@themoderncoderhow would you resolve a situation like that, it is a bit confusing
@@themoderncoderi guess it would be to rebase your new commits into the remote branch