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
{{ message }}
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.
We're starting to use this at work, and it looks awesome. However, the tools.json file only tracks commit hashes, which are not human friendly. There's no easy way to look and see what version of a tool we're requiring.
My suggestion would be to just add another field to the json, describing the requested tag/branch.
It would also be useful to have a field with the timestamp of the given commit hash, so it's more obvious if it's way out of date.
These two fields would only really be informational, the tool wouldn't need to read them at all, so I think it would be pretty easy to add (and thus would also likely be 100% backwards compatible).
I'd be happy to work on a PR if this is something that seems like it would be ok.
The text was updated successfully, but these errors were encountered:
Definitely a missing piece. The current way I hack this is to have a retool-install script that contains the retool add v1.0.1 ... commands that were run to do the install.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We're starting to use this at work, and it looks awesome. However, the tools.json file only tracks commit hashes, which are not human friendly. There's no easy way to look and see what version of a tool we're requiring.
My suggestion would be to just add another field to the json, describing the requested tag/branch.
It would also be useful to have a field with the timestamp of the given commit hash, so it's more obvious if it's way out of date.
These two fields would only really be informational, the tool wouldn't need to read them at all, so I think it would be pretty easy to add (and thus would also likely be 100% backwards compatible).
I'd be happy to work on a PR if this is something that seems like it would be ok.
The text was updated successfully, but these errors were encountered: