anchor.diff:  $ oc start-build nodejs-ex
   ----
   
  +[[developers-cli-troubleshooting]]
   == Troubleshooting
   
  -*Changing projects:*
  -
  -Although the `oc new-project` command automatically sets your current project to the one you've just created, you can always change projects by running:
  +*Changing Projects*
  +
  +Although the `oc new-project` command automatically sets your current project to
  +the one you've just created, you can always change projects by running:
   ----
   $ oc project <project-name>
   ----
  
positive.code: 
  // end::forking[]
  
  == Creating a Project
  
  To create an application, you must create a new project and specify the location of the source. From there, OpenShift begins the build process and creates a new deployment.
  
  . Log into OpenShift from the CLI:
  +
  * With username and password:
  +
  
negative.code: ====
  +
  The secret ensures that only you and your repository can trigger the build.
  . Run the following command to display the webhook URLs associated with your
  `*BuildConfig*`:
  +
  ----
  $ oc describe buildConfig <name>
  ----
  +
  . Copy the webhook URL output by the above command. If the above command does not
  display any webhook URLs, then no webhook trigger is defined for that build
  configuration.
  . Navigate to your forked repository on GitHub, then click *Settings*.
  . Click *Webhooks & Services*.
  . Click btn:[Add webhook].
  