anchor.diff:        "apiVersion": "v1beta1",
       }
   ----
  -
   ====
   +
   This defines the image repository that is tied to a Docker image repository
  
positive.code:           }
          }
  ----
  
  ====
  
  The payload URL is returned as the GitHub Webhook URL by the `describe` command
  
negative.code: the source code repository, where the build looks for the application source
  code. If your application exists inside a sub-directory, you can override the
  default location (the root folder) using this field.
  ====
  
  [[using-the-sti-environment-file]]
  == STI Environment File
  
  link:../image_writers_guide/sti.html[STI] enables you to set environment values
  in your application by specifying them in a *_.sti/environment_* file in the
  source repository. The environment variables are then present during the build
  process and in the final docker image. The complete list of supported
  environment variables are available in the documentation for each image.
  
  If you provide a *_.sti/environment_* file in your source repository, STI reads
  this file during the build. This allows customization of the build behavior as
  the *_assemble_* script may use these variables.
  
  For example, if you want to disable assets compilation for your Rails
  application, you can add `*DISABLE_ASSET_COMPILATION=true*` in the
  *_.sti/environment_* file to cause assets compilation to be skipped during the
  build.
  
  In addition to builds, the specified environment variables are also available in
  the running application itself. For example, you can add
  `*RAILS_ENV=development*` in the *_.sti/environment_* file to cause the Rails
  application to be started in `development` mode instead of `production`.
  
  == Build Triggers
  When defining a BuildConfig, you can define triggers to control the
  