Thank you for continuing to provide changes aimed at improving the development experience.
How about updating so that developers can also run buf format -w, buf lint, and buf breaking, and furthermore adding these steps to GitHub Actions so that any problematic changes are blocked by CI checks?
I acknowledge the changes of buf.yaml.

@YusukeShimizu
Appreciate the confirmation and comments.
I will try to support GitHub Actions.

@YusukeShimizu
I added job to run buf cli(buf-action) in github action workflow.(268c6b9)

• buf-action (https://github.com/marketplace/actions/buf-action).

Please check when you have time.
Thank you.

I think introducing buf-action is appropriate, and there’s no issue with the CI content.

[Q]It’s not entirely clear how developers are expected to run Buf commands (e.g., buf format -w) locally. We can generate code with “make all-rpc-docker,” but what should we do for other commands?
If you’re in the dev container, Buf is installed using “postCreateCommand,” but what happens in other cases? If there isn’t a provided method, I’d like to document that you either use Docker (like “make all-rpc-docker”) or individually install Buf yourself.

It seems that all-rpc is also a command that requires prior environment setup.
In line with the above considerations, it may be necessary to either update or remove it

Thank you for raising this question.

I recommend to install Buf Locally, developers can install Buf on their local machine following the official Buf installation guide and run the required commands directly.

Where would be the appropriate place to include the documentation, if necessary? Would it be acceptable to add it to the README?

I updated README and add usage_buf.md, please check.

I have added other commands, such as lint and format, to the Makefile, just like all-rpc.
c41c475