-
Notifications
You must be signed in to change notification settings - Fork 54
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
Feature: use .tool-versions #608
Conversation
0b78688
to
e982043
Compare
cdb762c
to
0f3b1fe
Compare
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.
Non blocking, but a question: Is .tool-version
an asdf thing or from somewhere else? I like the idea just haven't seen it that generic before and am curious
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.
It's kinda an asdf thing, though a few other tools are also interoperable with it: https://asdf-vm.com/manage/configuration.html#tool-versions
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.
Neat, thanks.
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 regularly use asdf, but LGTM
This is pretty basic, but it'll help when contributing to both community.hachyderm.io and nivenly.org, as they use different hugo versions, so installing them through a version manager such as
asdf
simplifies things.Rather than repeating the version twice, I parse the .tool-versions file for the hugo version, assuming we always use extended mode.