-
Notifications
You must be signed in to change notification settings - Fork 277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[question] buf - how to remove existing path #3426
Comments
Per the issue instructions, you must provide a reproducible example via a temporary GitHub repository. Without this, we are unable to help. Closing until a reproducible example is provided. |
@bufdev the gist of an example is the snippet I already provided above. Not complete, as in not a full repo that I can provide, sure. But it should explain the issue reasonably well. |
That is not a reproducible example. A reproducible example is something we can run, and see the issue. Please see the issue instructions for more details. |
Is there a link to the docs explaining how a path previously "tracked" by buf can be removed? Is there something to be done, or maybe just removing the |
We're not exactly sure what you're referring to here, and can't engage in this problem further until you've given us a reproducible example. Our team has limited bandwidth, and must be able to be efficient in its support requests. We won't be responding further to this issue until a reproducible example is provided, thanks. |
GitHub repository with your minimal reproducible example (do not fill out this field with "github.com/bufbuild/buf" or we will automatically close your issue, see the instructions above!)
No response
What's up?
Using a scala service with protobuf based grpc. I used to have 3 folders with .proto files in the service. One of those is now moved to a different library. So my buf.yaml was adjusted as follows:
When
buf breaking ...
is running (on my dev branch) it complains that:So the question is: How to properly get rid of the removed .proto path/folder ?
Thanks
The text was updated successfully, but these errors were encountered: