Danny Berger

That’s a clever thought. Do you think pipeline name is necessary? I’d probably prefer just the job name in order to keep it more concise and also to avoid different...

Thinking more, this would break the `check` behavior which expects to be able to look for specific statuses. Since those build arguments aren't available except for `out`, the independent `in`/`check`...

Just ran into this when trying to use `bosh create-env` to deploy a NAT box. Also [recently](https://cloudfoundry.slack.com/archives/bosh/p1479233098008062) came up on slack, although didn't fully diagnose it to this exact issue.

I added the following comment to the referenced issue that I initially started. I don't think svg+xml should necessarily be added as a default because I think there may be...

What operation is this occurring during: check, get, put? Are you sure your API token user has permissions for the repository you’re trying to edit?

I don't think I have seen this error before and, unfortunately, it's not easy to debug right now. Quickly reviewing some of the code, I think this could, theoretically, occur...

If you prefer, I believe you can `put` status updates to arbitrary commits (e.g. from pull requests) by setting `commit` to the PR checkout. Is that what you're looking for?...

I believe this property should be `lifeEvent` (singular) based on Naming Conventions from the [Style Guide](https://schema.org/docs/styleguide.html). I prepared [a commit](https://github.com/dpb587/fork-schemaorg-schemaorg/commit/44492168c14647c57db18fa90ea22561fe591b23) that anyone could directly merge or I could PR, but...