Skip to content
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

docs: Add instructions to update & verify scripts #255

Merged

Conversation

indradhanush
Copy link
Contributor

No description provided.

#
# Now checkout the appropriate branch for the Kubernetes version that
# you're building for. For example if you're building for Kubernetes
# 1.10.0 you would do the following:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you shorten this to "you would checkout release-1.10"? I don't think we need to explain everything ;)

Also, the tag is wrong.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually you know what, I was wrong on my second point. It's better to checkout the tag as you did, than the branch, as I did.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah didn't see the second comment. Fixing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed now.

@indradhanush indradhanush force-pushed the indradhanush/codegen-docs branch 2 times, most recently from a051039 to 816bf5e Compare April 24, 2018 14:56
#
# Now checkout the appropriate branch for the Kubernetes version that
# you're building for. For example if you're building for Kubernetes
# 1.10.0 you would do checkout the kubernetes-1.10.0 branch.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra "do", and please wrap kubernetes-1.10.0 in backticks 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed the extra "do".

Regarding the backticks, this is a bash comment? Sounds odd to me to add backticks the same way we don't do that in Golang comments. Is there a conventional practice I don't know about?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do that in Go comments as well ;)

Not sure if there's an official agreement but I think I've seen others do it as well.

@indradhanush indradhanush force-pushed the indradhanush/codegen-docs branch 2 times, most recently from 0c68438 to dd5f11b Compare April 25, 2018 14:28
#
# Now checkout the appropriate branch for the Kubernetes version that
# you're building for. For example if you're building for Kubernetes
# 1.10.0 you would checkout the `kubernetes-1.10.0 branch`.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

based on using this just now to fix my local setup, the branch name was release-x.x.x

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @elliott-davis. I've pushed a fix.

Copy link
Contributor

@krnowak krnowak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LFAD.

@krnowak krnowak dismissed asymmetric’s stale review April 27, 2018 06:40

The issues raised in the review are fixed.

@krnowak krnowak merged commit 1c2ed83 into habitat-sh:master Apr 27, 2018
@asymmetric asymmetric deleted the indradhanush/codegen-docs branch April 30, 2018 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants