This lesson's interactive features are locked, please to keep using them

Stash

You've been at MegaCorp™ for a while now (3 whole days!). And to your mother's surprise, you're still employed. Here's the workflow you've been using as a junior developer:

Commit some changes on your feature branch
Open a pull request from your feature branch to main
Checkout a new feature branch and start on the next task

Today however is a big day. The customers are complaining about a critical bug and the CEO saw you first. She's asked you to drop everything and fix it immediately... but you've got a bunch of unstaged changes that you're not ready to commit yet, and that you don't want to lose.

What do?

Many Git n00bs would create a second clone of the repo at this point (a huge mistake). You're better than that.

Git Stash

The git stash command records the current state of your working directory and the index (staging area). It's kinda like your computer's copy/paste clipboard. It records those changes in a safe place and reverts the working directory to match the HEAD commit (the last commit on your current branch).

To stash your current changes and revert the working directory to match HEAD:

git stash

To list your stashes:

git stash list

Click to play video

Assignment

While on main, update the README.md in the root of the megacorp repo to be:

# megacorp | good marketing example

MegaCorp™ is _the_ enterprise Customer Relationship Management (CRM) software. Not only is it an incredible product, but it also ships a programming language for "MegaCorp developers" that want to build custom features within the MegaCorp™ ecosystem. That language is called "Apux".

It was just after updating the README.md that the CEO approached you...

Stash the changes.
Once they're stashed, make sure they're safe by listing your stash. You should see a single stash in the list.

Run and submit the CLI tests.