-
Notifications
You must be signed in to change notification settings - Fork 817
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
Fix yaml file paths #339
Fix yaml file paths #339
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
This should probably actually point to the latest full release, rather than at master. Master is always going to be volatile. If you also want to make that change as well, that would also be appreciated. That being said, 0.4.0 will come out next Tuesday, so that could come next week. |
Build Failed 😱 Build Id: bc0af029-9509-489b-8584-7be126d5672d Build Logs
|
Build Succeeded 👏 Build Id: 8ca21f06-bbb1-4046-87c0-d58cdfccfe8b The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
I signed cla. @markmandel i rebased branch onto latest release. Thanks for your help! |
CLAs look good, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Build Succeeded 👏 Build Id: 57f0d490-3ceb-4812-b0c2-de7e550ed6a7 The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
No description provided.