You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a lot of tools we use including the hasura-cli and would like to keep the version consistent with team mates.
Currently everyone would have to manually keep the vesion in sync.
Describe the solution you'd like
We achieve this using https://asdf-vm.com/ which adds a .tool-versions file to the project (not hasura but user's project)
where we can set the version used and everyone just get's the same version and even in added to project's git history
I have also created the repository itself that helps install hasura-cli and would like to help hasura-cli users with the easy installation and use :)
Describe alternatives you've considered
alternative is maintain the version manually with communication. Not sue if this is feasible for remote teams.
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
We have a lot of tools we use including the hasura-cli and would like to keep the version consistent with team mates.
Currently everyone would have to manually keep the vesion in sync.
Describe the solution you'd like
We achieve this using https://asdf-vm.com/ which adds a
.tool-versions
file to the project (not hasura but user's project)where we can set the version used and everyone just get's the same version and even in added to project's git history
I have also created the repository itself that helps install hasura-cli and would like to help hasura-cli users with the easy installation and use :)
Describe alternatives you've considered
alternative is maintain the version manually with communication. Not sue if this is feasible for remote teams.
The text was updated successfully, but these errors were encountered: