-
Notifications
You must be signed in to change notification settings - Fork 828
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
Added list of various libs used in code #272
Conversation
Build Failed 😱 Build Id: 5e7b4126-74b2-4726-b419-3cfedfb1d7ca Build Logs
|
Build Succeeded 👏 Build Id: 013895a4-40d7-48b4-9b24-33fce7966b37 The following development artifacts have been built, and will exist for the next 30 days:
|
build/README.md
Outdated
- [pflag](https://github.com/spf13/pflag) | ||
- [viper](https://github.com/spf13/viper) | ||
- [grpc](https://godoc.org/google.golang.org/grpc) | ||
- [context](https://golang.org/pkg/context/) |
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.
I feel like context is a core library in go, so it's probably not worth listing here.
Do we want to just list everything in here:
https://github.com/GoogleCloudPlatform/agones/blob/master/Gopkg.toml
(Or conversely, just point people to it?)
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.
@enocom wdyt?
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.
A link for people unaware of dep's convention of using Gopkg.toml
might be nice.
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.
TIL! As a newcomer to Go I didn't know about Gopkg.toml so thanks for the lesson!
Happy to take any approach you see fit.
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.
I don't have strong opinions on this one.
Maybe something like "This project uses dep
(with link) as a dependency manager. You can see the list of dependencies here (link)"
That's probably the most valuable without having to (a) rewrite docs for another project (b) keep a list up to date in two places.
WDYT?
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.
SGTM!
Have working instructions for running Kubernetes 1.10 on top of minikube 0.28.0 - including a workaround for non default profiles. Since Agones works fine on k8s 1.10, figured it was worth making the move.
Found a line here that makes no sense.
Keeping up with Kubernetes versions, as well as providing us the functionality to do SubResources. Also will enable tightening up of permissions re: googleforgames#150
Build Succeeded 👏 Build Id: 113abedd-7344-467b-b2d2-cbd36b71201f The following development artifacts have been built, and will exist for the next 30 days:
|
Build Failed 😱 Build Id: 0ff54c5a-0947-4f59-b87d-dd14e2cf684d Build Logs
|
I've seen this practice in other open source git repos and find it rather useful so wanted to propose adding it :)
To me it serves two goals: