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
Is your feature request related to a problem? Please describe
If a asdf plugin is broken due to a changed tool URL, while a fix PR is pending on the original archive I often fork and fix the issue in my own issue. While using my own fixed asdf plugin, I have to manually install this plugin, which is awkward for my CI system.
Describe the proposed solution
I would like to see the option of specifying a plugin URL in the .tool-versions file that can be used to override the URL of a particular plugin in the plugin repository. An "adsf plugin-add " command should check for this value in preference to the default repo value
Describe similar asdf features and why they are not sufficient
Manually scripting a asdf plugin add, which is a different workflow when adding a default asdf plugin
Describe other workarounds you've considered
Manually specifying every plugin URL rather then take advantage of the URLs in the
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
If a asdf plugin is broken due to a changed tool URL, while a fix PR is pending on the original archive I often fork and fix the issue in my own issue. While using my own fixed asdf plugin, I have to manually install this plugin, which is awkward for my CI system.
Describe the proposed solution
I would like to see the option of specifying a plugin URL in the .tool-versions file that can be used to override the URL of a particular plugin in the plugin repository. An "adsf plugin-add " command should check for this value in preference to the default repo value
Describe similar
asdf
features and why they are not sufficientManually scripting a asdf plugin add, which is a different workflow when adding a default asdf plugin
Describe other workarounds you've considered
Manually specifying every plugin URL rather then take advantage of the URLs in the
The text was updated successfully, but these errors were encountered: