There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
Agree with a comment or answer? Like () to up-vote the contribution!
1. Switch to the fencing branch from the master branch.
However, it throws an error that ‘fencing’ isn’t a known filepath to git, so you need to go back and create the branch again. Not a huge problem, but since creating the branch isn’t included in the steps, it makes you feel like you are doing something wrong.
Okay, we learned that the checkout command can change your working directory in the last module.
Say I made some changes to my working directory while checked out on the fencing branch and then used checkout master. Would that mess up all the work I hadn’t yet committed to fencing?
I know this is so very late, but I believe that would be a good time to use the git stash command. Then you can save the changes you made in your working directory so you don’t lose your work so that you can then switch branches without it complaining to you about it. When you are done working on the branch you switched to and ready to switch back to the branch you had saved a stash for, you can switch back and use the git stash pop command to continue making changes to the working directory. Also, the git stash list command will show you a list of the stash history
) below.
) to up-vote the contribution!