anchor.diff:  
   Therefore, your pull requests will have to be handled manually in your Kanban workflow. More below.
   
  -* create an additional repository for the QA person, who becomes the collaborative development partner (like Bill in the web page writeup).
  -
  -=== Develop a new feature
  -
  -* create a new feature development branch
  -
  -* `git checkout -b some-feature master`
  -
  -(give it a name appropriate to your new feature)
  +=== Identify a new feature
  +
  +
  +=== Write a new story
  +
  +
  +=== Develop the new feature
  +
  +
  +
  +Here we will create a new feature development branch by using the `git checkout -b some-feature master` command.
  +
  +(You will give your feature a name appropriate to your new feature)
   
   Go:
   
  
positive.code: 
  Look at your Jenkins console. Why didn't the build run? Investigate the hijoInit configuration. Don't move on until you see why.
  
  Developer, take your Kanban task and move it to QA.
  
  === Test the new feature
  QA, once you have received the task from the developer:
  
  Starting as your public ID, log into manos:
  
negative.code: }
  ....
  
  Exit nano; you can now `sudo ant` and it should work.
  
  Let's display your new functionality to the world:
  
  