anchor.diff:  // tag::using-a-proxy-for-git-cloning-1[]
   
   If your Git repository can only be accessed using a proxy, you can define the
  -proxy to use in the `*source*` section of the `*BuildConfig*`. You can configure
  +proxy to use in the `source` section of the `BuildConfig`. You can configure
   both a HTTP and HTTPS proxy to use. Both fields are optional.  Domains for which
   no proxying should be performed can also be specified via the *NoProxy* field.
   
  
positive.code: 
  [NOTE]
  ====
  Files located at the `*scripts*` URL take precedence over files located in
  *_.s2i/bin_* of the source repository. See the
  xref:../creating_images/s2i.adoc#creating-images-s2i[S2I Requirements] topic and the
  link:https://github.com/openshift/source-to-image/blob/master/docs/builder_image.md#sti-scripts[S2I
  
negative.code: [NOTE]
  ====
  You can also use xref:combinations[combinations] of the these configurations
  to meet your specific needs.
  ====
  
  All source secrets must be linked to the builder account and added to the build
  configuration using the following instructions:
  
  . Add the secret to the builder service account. Each build is run with
  the *builder* role, so you must give it access to your secret with the
  following command:
  +
  ====
  