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
I would like to be able to only install some tools in CI/CD. This is equivalent to devDependencies and dependencies in the package.json file but in my proposal it's mich more flexible.
Now just running proto use would install every tool specified (this could also only install tool-a). If proto use --profile prod is run only tool-d is installed (this could alson install tool-a and tool-d).
This could be entirely optional in .prototools. The profiles must be prefixed with profile., otherwise there could be confusion between a profile plugins and the plugin URLs.
Thanks, Frederik
The text was updated successfully, but these errors were encountered:
I would like to be able to only install some tools in CI/CD. This is equivalent to
devDependencies
anddependencies
in the package.json file but in my proposal it's mich more flexible.Consider we have the following .prototools file:
Now just running
proto use
would install every tool specified (this could also only install tool-a). Ifproto use --profile prod
is run only tool-d is installed (this could alson install tool-a and tool-d).This could be entirely optional in .prototools. The profiles must be prefixed with
profile.
, otherwise there could be confusion between a profileplugins
and the plugin URLs.Thanks, Frederik
The text was updated successfully, but these errors were encountered: