bufdev
bufdev
@saquibmian this is low priority, no need for this for now
I'd say the default behavior of `buf format -w` should be to not modify the file if it has not changed - if you can put up a PR that...
We'd need to see your `buf.yaml` files to comment fully, but this likely means that you have `name: buf.build/company/common` in `common/buf.yaml`. The warning is valid - if you have a...
If you can provide a specific, reproducible example, we can look into it - perhaps in a temporary GitHub repo.
Closing as we don't have a reproducible example - if you add one, we'll reopen, thanks.
@akshayjshah's favorite project :-) we'll do this at some point.
I know this won't be the best answer for your use case here, but Buf won't have the ability to add custom lint or breaking change checks. The goal of...
Correct, this is not on the roadmap.
When we do get to this, make sure that https://github.com/bufbuild/buf/issues/1906 is addressed as well.
Can you explain what the use case is for this?