anchor.diff:  this behavior.
   ====
   
  +To pass this payload using `curl`, define it in a file named *_payload_file.yaml_* and run:
  +
  +----
  +$ curl -H "Content-Type: application/yaml" --data-binary @payload_file.yaml -X POST -k https://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic
  +----
  +
  +The arguments are the same as the previous example with the addition of a header and a payload. The `*-H*` argument sets the `*Content-Type*` header to `*application/yaml*` or `*application/json*` depending on your payload format. The `*--data-binary*` argument is used to send a binary payload with newlines intact with the `*POST*` request.
  +
   [[describe-buildconfig]]
   
   *Displaying a BuildConfig's Webhook URLs*
  
positive.code: ----
  http://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/generic
  ----
  
  The endpoint can accept an optional payload with the following format:
  
  
negative.code: trigger on your `*BuildConfig*` and trigger it via your Gogs server also.
  ====
  
  Given a file containing a valid JSON payload, you can manually trigger the webhook via `curl`:
  
  ----
  $ curl -H "X-GitHub-Event: push" -H "Content-Type: application/json" -k -X POST --data-binary @github_payload_file.json https://<openshift_api_host:port>/oapi/v1/namespaces/<namespace>/buildconfigs/<name>/webhooks/<secret>/github
  ----
  
  The `*-k*` argument is only necessary if your API server does not have a properly signed certificate.
  
  *Generic Webhooks*
  
  