[Do not merge] Prototype GitHub workflows #4
Annotations
10 errors and 1 warning
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L27
symbol "buf.registry.module.v1.Digest" already defined at buf/registry/module/v1/digest.proto:27:9
|
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L29
symbol "buf.registry.module.v1.Digest.type" already defined at buf/registry/module/v1/digest.proto:29:14
|
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L34
symbol "buf.registry.module.v1.Digest.value" already defined at buf/registry/module/v1/digest.proto:34:9
|
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L38
symbol "buf.registry.module.v1.DigestType" already defined at buf/registry/module/v1/digest.proto:38:6
|
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L39
symbol "buf.registry.module.v1.DIGEST_TYPE_UNSPECIFIED" already defined at buf/registry/module/v1/digest.proto:39:3; protobuf uses C++ scoping rules for enum values, so they exist in the scope enclosing the enum
|
Buf breaking:
.base/buf/registry/module/v1/digest.proto#L41
symbol "buf.registry.module.v1.DIGEST_TYPE_B5" already defined at buf/registry/module/v1/digest.proto:41:3; protobuf uses C++ scoping rules for enum values, so they exist in the scope enclosing the enum
|
Buf breaking:
.base/buf/registry/module/v1beta1/digest.proto#L27
symbol "buf.registry.module.v1beta1.Digest" already defined at buf/registry/module/v1beta1/digest.proto:27:9
|
Buf breaking:
.base/buf/registry/module/v1beta1/digest.proto#L29
symbol "buf.registry.module.v1beta1.Digest.type" already defined at buf/registry/module/v1beta1/digest.proto:29:14
|
Buf breaking:
.base/buf/registry/module/v1beta1/digest.proto#L34
symbol "buf.registry.module.v1beta1.Digest.value" already defined at buf/registry/module/v1beta1/digest.proto:34:9
|
Buf breaking:
.base/buf/registry/module/v1beta1/digest.proto#L38
symbol "buf.registry.module.v1beta1.DigestType" already defined at buf/registry/module/v1beta1/digest.proto:38:6
|
Buf setup
No github_token supplied, API requests will be subject to stricter rate limiting
|
Loading