From the course: Version Control for Everyone

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Stashing work that's not ready yet

Stashing work that's not ready yet - GitHub Tutorial

From the course: Version Control for Everyone

Start my 1-month free trial

Stashing work that's not ready yet

“

- [Instructor] In this video, we're going to look at stashing changes, which is a way to temporarily squirrel away work that isn't considered done enough to commit, but needs to be preserved while we go and work on something else. So there may be times when you're working on a branch, the work isn't finished yet, you don't think it's ready, but you have to switch to another branch to work on something. This is where we use them. I'll reset my work environment here by checking out the master branch and then subsequently, I'm going to go back to the fewer FAQs branch that I'm working on. Switching back over to my editor, I have the FAQ dot Markdown file open. And I'm happily working away on this. Removing questions, that aren't as frequently asked. At this point, when I'm working on this branch, I get a note from somebody that I'm collaborating with that something in the migration file should be updated. Switching back to…

Contents