Aaron Crickenberger d0b259597a Use OWNERS-based labeling for kind/api-change ...

This replaces the following path-label munger config, except
we're using kind/api-change for everything instead of two
different kind/ labels

```
^pkg/api/([^/]+/)?types.go$    kind/api-change
^pkg/api/([^/]+/)?register.go$ kind/new-api
^pkg/apis/[^/]+/([^/]+/)?types.go$    kind/api-change
^pkg/apis/[^/]+/([^/]+/)?register.go$ kind/new-api
```

2018-08-10 13:48:56 -07:00

..

endpoints

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

events

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

legacyscheme

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

persistentvolume

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

persistentvolumeclaim

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

pod

Retain ShareProcessNamespace in pod storage

2018-07-24 15:55:09 +02:00

ref

Add missing error handling in schema-related code

2018-06-23 21:06:32 +10:00

resource

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

service

Autogenerated: hack/update-bazel.sh

2018-02-16 13:43:01 -08:00

testapi

autogenerated

2018-08-09 19:35:03 +03:00

testing

Remove references to 'pkg/apis/componentconfig/install' and fix inconsistencies

2018-08-09 18:45:27 +03:00

v1

Run hack/update-bazel.sh

2018-06-22 16:22:57 -07:00

OWNERS

Use OWNERS-based labeling for kind/api-change

2018-08-10 13:48:56 -07:00