Skip to content

Mechanism for forcing a golint update #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

Merged
merged 1 commit into from
Oct 17, 2017
Merged

Mechanism for forcing a golint update #19

merged 1 commit into from
Oct 17, 2017

Conversation

wfleming
Copy link
Contributor

They don't version releases, so it's always a matter of installing
whatever's latest. Similar to some other projects, I've added a file we
can touch to force expire docker layer caches & get a new version.

They don't version releases, so it's always a matter of installing
whatever's latest. Similar to some other projects, I've added a file we
can touch to force expire docker layer caches & get a new version.
@ABaldwinHunter
Copy link
Contributor

Nice

@ABaldwinHunter
Copy link
Contributor

Do we want to do something similar on gofmt and govet?

@wfleming
Copy link
Contributor Author

Do we want to do something similar on gofmt and govet?

Both of those are packaged with golang itself, so for them it's a matter of changing the base image.

@wfleming wfleming merged commit a1a3ea1 into master Oct 17, 2017
@wfleming wfleming deleted the will/bump-golint branch October 17, 2017 19:35
@levinalex levinalex mentioned this pull request Oct 18, 2017
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.

2 participants