Steve Durrheimer

This could probably be solved by moving to GoReleaser, which we are planning to do in the near future.

Okay looks like the current way to do this is: ```jsonnet local s = t.store(commonConfig { replicas: 1, serviceMonitor: true, }) + { statefulSet+: { spec+: { template+: { spec+:...

@betorvs By looking [here](https://github.com/thanos-io/kube-thanos/blob/master/jsonnet/kube-thanos/kube-thanos-store-shards.libsonnet#L19), we can see that the store shards need an additional `shards {}` enclosure. You can try: ```jsonnet }) + { shards+: { statefulSet+: { spec+: {...

Also it is true that in the case of systemd, adding `ListenStream` directives to the `docker.socket` systemd unit file is a better approach than adding `tcp://` `hosts` configs in the...

@cpuguy83 ``` IMPORTANT: Docker 1.12 ships with an updated systemd unit file for rpm based installs (which includes RHEL, Fedora, CentOS, and Oracle Linux 7). ``` For `rpm` based systems...

It exits with a code 0 because it's a warning, not a error.

Agreed, `fixup!` and `squash!` prefixes should be ignored as those mechanisms are part of the base features Git offers.

Will do as soon as I get some time for it.

Actually, for me (and probably for others like @fabxc), I think it is less-confusing to have `1.6` as a shortcut for the latest `1.6.x` version. Lately, we got confused because...

We could yes, but it is already possible to execute another command by using the `--entrypoint` option.