Ben Boeckel

It seems that the follow logic considers the empty string a "key" when generating follow strings. I use 5 characters for follow (to keep it to a one-hand home row)...

`yaml-merge-keys` developer here. It supports `serde-yaml` using the `serde_yaml` feature. We use it in our code just fine.

I looked into it and it [now seems possible](https://github.com/onur/docs.rs/pull/73) to specify features for documentation builds. I'll do that for the crate.

Ah, I had done so, but hadn't made a release since then.

I've just published 0.2.1.

I've seen multiple parsers get very loose around the merge key spec. Apparently this is valid for the Ruby parser: ```yaml foo:

See https://crates.io/crates/yaml-merge-keys for an implementation of the spec.

Also, this is a duplicate of #68.

The homepage says that GitLab is supported now, but does this mean just `gitlab.com`? Or are self-hosted public instances also supported?

coveralls.io has an icon in the top-left saying that Bitbucket and GitLab are now supported.