anchor.diff:  
   *Reminder: the person leading the lab at this point should be the developer.*
   
  -If your feature is passing your tests, you can push it to origin, but NOT master. As suggested in the Atlassian web tutorial, push it to your feature branch, in this case "add-numbers":
  -
  -....
  -vagrant@manos5:/home/hijo$ git push origin add-numbers
  +If your feature is passing your tests, you can push it to origin, but NOT master. As suggested in the Atlassian web tutorial, push it to your feature branch, in this case "feature/add-numbers":
  +
  +....
  +vagrant@manos5:/home/hijo$ git push origin feature/add-numbers
   Counting objects: 29, done.
   Compressing objects: 100% (10/10), done.
   Writing objects: 100% (17/17), 1.34 KiB | 0 bytes/s, done.
  
positive.code: vagrant@manos5:/home/QA/hijo$ git show-branch -a
  * [master] initial commit
   ! [origin/HEAD] initial commit
    ! [origin/add-numbers] sum feature
     ! [origin/master] initial commit
  ----
    +  [origin/add-numbers] sum feature
    +  [origin/add-numbers^] testing new branch
  *+++ [master] initial commit
  ....
  
  Ah, the developer said  I needed to be on the add-numbers branch.
  
  ....
  vagrant@manos5:/home/QA/hijo$ git checkout add-numbers
  Branch add-numbers set up to track remote branch add-numbers from origin.
  Switched to a new branch 'add-numbers'
  
  vagrant@manos5:/home/QA/hijo$ cat src/main/java/biz/calavera/Class1.java
  package biz.calavera;
  
negative.code: Switched to branch 'master'
  vagrant@manos5:/home/hijo$ ls
  build.xml  src  target
  vagrant@manos5:/home/hijo$ git checkout feature/add-numbers
  Switched to branch 'feature/add-numbers'
  vagrant@manos5:/home/hijo$ ls
  build.xml  src  target  x
  
  ....
  
  See how that works? The file "x" is visible in the "feature/add-numbers" branch, but not in the master branch. Delete it:
  
   vagrant@manos5:/home/hijo$ rm x
  
  