James Hegedus

`ASDF_GLOBAL_TOOL_VERSIONS_PATH` would still require more work from this PR to actually work though, as current lookup of Global is at `$HOME/ADSF_DEFAULT_TOOL_VERSIONS_FILENAME`. We would need to change the lookup method.

I'm not opposed to changing the plugins dir location, but why not make this a configuration option of the existing `.asdfrc` config file?

This thread seems related to #531 Still awaiting feedback in potential fix PR #1236

`asdf install` in the GitHub Action is completely different to `asdf install` on you local machine. This is cause for confusion and I would like to dial back the GitHub...

I like this feature request. Since the plugins are git repos, I believe this logic could easily live in the core. TTL cache is a great idea. We could use...

Yes it should, and I imagine the code for this would be the same just with the repo URL being targeted as the only difference

I'm confident this will be the same code so renaming this Issue to cover the core asdf tool as well.

Yes, there's currently no solution for auto-updating the plugins. I have some ideas around this aside from just the message.

@jsejcksn Those ideas were more around how we handle sourcing plugins in general and plugin versioning. For reference, here's the Issue requesting plugin versions https://github.com/asdf-vm/asdf/issues/166 I'll start work on this...

>Since we rely on master branches for plugins (atleast from what I remember) On `asdf plugin add ` the default branch of the remote is used. It's only on `asdf...