Update rules_go to 0.7.0

[dougkoch]

As an Ubuntu user, I had the same issue with rules_go that @genehwung mentioned in #26. This has since been fixed by bazel-contrib/rules_go#850

[bazel-io]

Can one of the admins verify this patch?

[achew22]

Check this please

[dougkoch]

Jenkins, test this please

[achew22]

@damienmg, I just added @dougkoch as a contributor to this project. Do I need to do more to whitelist him to run PRs in Jenkins?

[damienmg]

Andrew: they need to add 2FA then I can add them to the bazelbuild org and follow-up

…

On Sun, Nov 12, 2017 at 11:07 PM Andrew Z Allen ***@***.***> wrote: @damienmg <https://github.com/damienmg>, I just added @dougkoch <https://github.com/dougkoch> as a contributor to this project. Do I need to do more to whitelist him to run PRs in Jenkins? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADjHf-h0QeejDCgNnCWA-5n-Y0QaMuEFks5s1-qzgaJpZM4QauMS> .

[dougkoch]

@damienmg I just enabled 2FA

[damienmg]

I invited you to the bazelbuild org, once you accept, go to https://github.com/orgs/bazelbuild/people?utf8=%E2%9C%93&query=dougkoch and in front of your name, on the third column, change "Private" to "Public" so your profile show you are in the bazelbuild org. Once done so, you will have the power to trigger our CI, every PR from you will automatically trigger it and you will be able to trigger it with the sentence "test this please". Make sure to eyeball a PR for security aspect before triggering a build.

…

On Mon, Nov 13, 2017 at 11:27 AM Doug Koch ***@***.***> wrote: @damienmg <https://github.com/damienmg> I just enabled 2FA — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADjHf4tI6FOwsldUCRpxeYdrBd20Bm9Nks5s2JgKgaJpZM4QauMS> .