Temporarily store some work in progress because I have to jump to another branch
We all know this. You’re working on some new feature and you have lots of “work in progress”. Then an urgent issue comes in, you have to jump onto the master and apply a hotfix. In this lesson we will learn how to temporarily store your current changes s.t. you can switch the current branch and come back later to resume your work again.
Good course. I'm think you could add some useful examples to use git reflog, this command has been save me the life more than once. And maybe add some about git flow.
Hi Miguel. Thanks for the feedback. Yep indeed, I'm already drafting some more lessons I'll be adding to the course very soon. Git reflog is one of them, among bisect and a couple of others. So stay tuned 😉.
Useful course, well done. As a heads up, git stash save is deprecated. From the manual (v2.20.1): This option is deprecated in favour of git stash push. It differs from "stash push" in that it cannot take pathspecs, and any non-option arguments form the message.
@JP oh thx for the heads up 👍
Thanks for your effort. Apart from this git examples, I would like to see some of "git flow" examples by you. I'm sure that it'll be useful. Thanks.
I would like to see some of "git flow" examples by you. I'm sure that it'll be useful. Thanks.
Thanks, I'm definitely thinking about something like that. Not sure whether it would be about the "flow model" but rather more in the direction of the trunk based development approach with git.
Hi, great course, I learned new stuff watching it :)
One minor thing that I've noticed and that I think you can improve is: In every lesson you are doing git add . to stage all files that have been modified and then you are doing git commit -am but here in this command -a is unnecessary because you've already added changed files to stage area with previous command, so git commit -m is sufficient here :).