We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As far as I understand, git branches and tags are types of git refs (they are stored under .git/refs).
.git/refs
IMO it should therefore be possible to use the ref option as a generic way for referencing commits, branches, and tags.
ref
This is actually stated in the documentation:
Any ref that is a valid input to git checkout is accepted.
https://buf.build/docs/reference/inputs#other-options
However, while git checkout remote-tag is working, buf generate "ssh://[email protected]/path-to-repo.git#ref=remote-tag" is not.
git checkout remote-tag
buf generate "ssh://[email protected]/path-to-repo.git#ref=remote-tag"
IMO this feature would make parameterizing CI pipelines easier, e.g.:
ssh://[email protected]/path-to-repo.git#ref=develop
ssh://[email protected]/path-to-repo.git#ref=v1.0.0
Note: this is also how kubectl kustomize is implementing the refoption:
ref - a git fetch-able ref, typically a branch, tag, or full commit hash (short hashes are not supported)
https://github.com/kubernetes-sigs/kustomize/blob/master/examples/remoteBuild.md#remote-directories
The text was updated successfully, but these errors were encountered:
I can reproduce this with:
buf build "https://github.com/bufbuild/buf.git#ref=v1.27.0,subdir=proto"
The same works when I use tag:
tag
buf build "https://github.com/bufbuild/buf.git#tag=v1.27.0,subdir=proto"
Thank you for reporting, we'll look into this.
Sorry, something went wrong.
No branches or pull requests
As far as I understand, git branches and tags are types of git refs (they are stored under
.git/refs
).IMO it should therefore be possible to use the
ref
option as a generic way for referencing commits, branches, and tags.This is actually stated in the documentation:
https://buf.build/docs/reference/inputs#other-options
However, while
git checkout remote-tag
is working,buf generate "ssh://[email protected]/path-to-repo.git#ref=remote-tag"
is not.IMO this feature would make parameterizing CI pipelines easier, e.g.:
ssh://[email protected]/path-to-repo.git#ref=develop
- build against latest changes on the develop branchssh://[email protected]/path-to-repo.git#ref=v1.0.0
- build against a stable release tagNote: this is also how kubectl kustomize is implementing the
ref
option:https://github.com/kubernetes-sigs/kustomize/blob/master/examples/remoteBuild.md#remote-directories
The text was updated successfully, but these errors were encountered: