The default path when callling a provider should be rethought. All is fine when you are calling a provider locally but things are ambiguous when one callls a remote provider. In this case the working directory is inside the providers dir (ie ~/.config/tackle/providers/<>/<>) which almost all the time is undesirable.
Problem is that providers in general should not be mutated. When creating a provider, one expects to have all the files / directories you are operating against local to the calling directory except for things like generate / copy where the input should be local to the provider.
Hooks that expect to be called from local provider:
generate
Copy
Same as above
tackle org/repo
The callling dir is passed through and so all outputs from generate are right
Remote provider never calls local tackle. Thus the path should always be in the remote
?
Ambiguous hook calls
command Githubissues.
Githubissues is a development platform for aggregating issues.
The default path when callling a provider should be rethought. All is fine when you are calling a provider locally but things are ambiguous when one callls a remote provider. In this case the working directory is inside the providers dir (ie ~/.config/tackle/providers/<>/<>) which almost all the time is undesirable.
Problem is that providers in general should not be mutated. When creating a provider, one expects to have all the files / directories you are operating against local to the calling directory except for things like generate / copy where the input should be local to the provider.
Hooks that expect to be called from local provider:
Ambiguous hook calls