Noel Yap

I run into this issue even when both `buf.yaml` and `buf.work.yaml` are provided: ``` $ gzip -cdq buf-format-workspace.tar.gz | tar xfpv - $ cd buf-V1PhXJYv/buf/testdata/buf/testdata/proto/image $ buf format --diff testdata.proto...

FWIW, I use `PROMPT_COMMAND` to set `PS1` (in `bash`). You might want to try that.

@vearutop , I had initially started doing just that and learned that if the implementations are long, that becomes unwieldy (not to mention it not lending itself well to sharing...

Sorry, I was unclear. By scenario context, I had meant context specific to the scenarios being tested, not `godog.ScenarioContext`. One way to resolve that would be to allow `godog.ScenarioContext` to...

As I was trying that out, I realized there's still a bunch of jumping around in the code since `longStep1`, etc would still need to be called explicitly.

AFAIK, there have been no actual releases but now it occurs to me that I may not have been looking in the right place for any released artifacts. Are there...

Yes, I understand that. What are the steps for those binaries to be published there? Can, for example, someone insert malicious source, build it, then publish the binaries to that...

I had thought of generating a SHA file but it occurred to me that it has the same issue. One can make a file change, build the artifact and the...

The legwork of putting in place a good release process for `protolock`. I don't know enough to choose among the various tools, etc. It sounds like you and Steve are...

I'm OK with this so long as there's an audit trail from the binary back to the source.