Doria Keung

I've added it to an issue we already have in `buf` to improve the error message. Thanks for filing this!

We have a couple of options on how we can handle this: 1. We can use `onStartupFinished` flag under activation events (which is recommended over `*`). This will give the...

Yes, this action should support `with.branch`, we are currently in the process of moving our workflows towards branches, so we have not quite updated this action yet. We will be...

This has been addressed in https://github.com/bufbuild/buf/pull/3206

Thank you for providing a clear example. In the use-case of Twirp, specifically, is there a reason why you would need `include_imports` for the `protoc-gen-twirp` plugin? For that particular use-case,...

You are correct in that you cannot restrict plugin configurations by input in `v2` and you've correctly ascertained our current guidance is to maintain a `buf.gen.yaml` configuration for each combination...

I posted a response earlier, but went through your footnotes and I see that your intended proto root is the root of your source repository. For the `includes` key, we'll...

Thank you for the response! I'm going to do some investigation on some potential improvements we can make on the build path, the size/repository setup is definitely the contributing factor...

Thank you @emcfarlane for putting up a PR for adding the `includes` key to the JSON schema https://github.com/SchemaStore/schemastore/pull/4753

> Gentle ping :) Is there any progress on this issue? Hello! So for transparency, we are currently tackling working on issues one layer at a time, starting with the...