anchor.diff:  commit because using the `--depth=1` option only works with named branch refs.
   
   If you want to perform a full Git clone of the `master` for the specified
  -repository, you can set the `*ref*` to `master`. 
  +repository, you can set the `*ref*` to `master`.
   
   [[using-a-proxy-for-git-cloning]]
   
  
positive.code: <6> An optional secret provided if credentials are needed to access the input image.
  ====
  
  NOTE: This feature is not supported for builds using the `*Custom*` strategy.
  
  [[using-secrets]]
  == Using Secrets During a Build
  
negative.code: 
  === Image Source
  
  Additional files can be provided to the build process via images. Input images
  are referenced in the same way the `*From*` and `*To*` image targets are
  defined. This means both Docker images and image stream tags can be referenced.
  In conjunction with the image, you must provide one or more path pairs to
  indicate the path of the files/directories to copy out of the image and the
  destination to place them in the build context.
  
  The source path can be any absolute path within the image specified. The
  destination must be a relative directory path. At build time, the image will be
  loaded and the indicated files and directories will be copied into the context
  directory of the build process. This is the same directory into which the source
  repository content (if any) is cloned. If the source path ends in *_/._* then
  the content of the directory will be copied, but the directory itself will not
  be created at the destination.
  
  Image inputs are specified in the `*source*` definition of the `*BuildConfig*`:
  
  