protocolbuffers / protocolbuffers/protocolbuffers.github.io

Proto Best Practices — references to googleapis/googleapis common objects

Open
#254 19 comments 0 reactions 1 assignee View on GitHub

@jguamie is already working on this.

Since Oct 17, 2025.

Dominant language
HTML
Stars
69
Forks
179
PR merge metrics
No merged PRs in 30d

Description

👋🏻 hey folks!

Not sure if this is an actual issue or just missing documentation, so feel free to point me out to the right place.

I am wondering how do people deal with "common" protobuf messages that are referenced in the "Proto Best Practices" document but are not shipped with the protoc compiler. I am talking about google.types.* specifically here, which are located in the googleapis/googleapis. Feels a bit strange relying on someone's else API schemas.

  • Why aren't these messages part of the well-known types shipped with the protobuf?
  • How do people generally make them available in the CI and to the developers? Copy? Clone? Use googleapis/api-common-protos?
  • Does it make sense to include these into the protocolbuffers project itself?

Thanks in advance!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.