-
Notifications
You must be signed in to change notification settings - Fork 19
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
Handle go-groups differently #222
Comments
Let's build this into the dev base image. I've seen a few build failures related to oss.indeed.com being out. Building it into the container should remove the need to fetch the dependency. |
mjpitz
added
effort: 2
good first issue
Good for newcomers.
help
type: fix
Iterations on existing features or infrastructure.
labels
Feb 20, 2021
We'll probably want to do this for all the dev tools tbh. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing 503's fetching go-groups again from Indeed. One way to insulate us from this is by caching the binary in a container.
The text was updated successfully, but these errors were encountered: