Doria Keung

Along the same lines, when we are returning errors to users around imports, we should indicate that in the error: https://github.com/bufbuild/buf-lint-action/issues/10

Also, I think that this metadata file can include information such as the license information (reference #682 and #488). As for the shape of the information, we could consider having...

We recently added `except` and `override` keys for ruby and csharp and `default` for obj-c prefix, and I'm currently reviewing the PHP use-case. I want to make sure we capture...

Tags are now labels, and labels are mutable: https://buf.build/docs/concepts/commits-labels#labels Going to close this for now, feel free to re-open if there are any questions or concerns.

> Does the new v2 `buf.gen.yaml` work this way? > > can the path be not finite? like just acme/weather/v1 ? Yep! So for `v2`, you can now specify a...

Just addressing this issue as a whole, we've added `php_metadata_namespace_suffix` as a part of the new managed mode options: https://buf.build/docs/generate/managed-mode#file-options We've also reworked the way managed mode works in `v2`...

Closing this for now since the above queries have been answered, please feel free to either re-open or create a new issue for any concerns., thanks!

Hi, so this behaviour is greatly improved for `v2` modules and workspaces: https://buf.build/docs/configuration/v2/buf-yaml Dependencies for `v2` workspaces is now defined across the entire workspace, so it should make it much...

We've made improvements to this in `v2` of `buf.gen.yaml`, where you can define the inputs for each configuration file. You will still need to define a configuration file for each...

Given the provided guidance to migrate to `v2`, we are closing this as a duplicate of the feature request #3060.