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
Can you change the release tag to match the pattern? I can see us using this in the future to help constrain our cookbooks to a specific version when using this tool. https://github.com/websterclay/knife-github-cookbooks
IE: KV in consul to represent community cookbook and currently desired push to chef.
cookbook: "git@github.com:johnbellone/consul-cookbook.git" version: "v0.8.3"
git init
git remote add origin git@github.com:johnbellone/consul-cookbook.git
git fetch origin v0.8.3
git reset --hard FETCH_HEAD
The text was updated successfully, but these errors were encountered:
I now see that the v0.10.0 tag exists just not the release. Which I think as long as the tag exists it should likely be fine in my case.
Sorry, something went wrong.
I modified the release so that it points to v0.10.0.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
No branches or pull requests
Can you change the release tag to match the pattern? I can see us using this in the future to help constrain our cookbooks to a specific version when using this tool. https://github.com/websterclay/knife-github-cookbooks
IE: KV in consul to represent community cookbook and currently desired push to chef.
cookbook: "git@github.com:johnbellone/consul-cookbook.git"
version: "v0.8.3"
git init
git remote add origin git@github.com:johnbellone/consul-cookbook.git
**Note: the full history of this commit will be retrieved
git fetch origin v0.8.3
git reset --hard FETCH_HEAD
The text was updated successfully, but these errors were encountered: