Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • POKE. Thank you!! You answered my question and more. That additional code you provided is exactly what I intended to do, but I did not have the time to figure it out. Your answer is very clear. Thank you, thank you.
    – Jennings
    Commented Feb 14, 2018 at 22:52
  • 1
    @Jennings I’m glad I could help you! :) – Please remember to accept the answer if this answers the question to mark it as resolved.
    – poke
    Commented Feb 14, 2018 at 23:03
  • I see a similar answer in the other thread now, which was praised for it's brevity. Didn't want to try it since there plenty comments warning about losing work. Thank you for the thorough explanation.
    – Jennings
    Commented Feb 14, 2018 at 23:09
  • 3
    An important thing to remember is that it’s actually pretty difficult to lose work with Git. Once you have committed something, you are pretty safe, so you don’t need to be scared about it. It’s just sometimes more complicated to recover than other times. But by creating branches, you can very easily create backup pointers for you to recover easily later one in case you need it :)
    – poke
    Commented Feb 14, 2018 at 23:15