We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forge shape circleci/node@5.1.0/install would be cool. Thoughts from first iteration:
forge shape circleci/node@5.1.0/install
main issue here is the lack of clarity on what directory should do what. for concourse resources the working directory is the only thing that the resource is supposed to interact with for github actions its GITHUB_WORKSPACE (working dir) RUNNER_TEMP and RUNNER_TOOLCACHE which all have relatively clear mappings for these its...the whole file system. there's no "standard" where Orbs install tools, etc. so its pretty unclear how the CLI should expose them, if at all
main issue here is the lack of clarity on what directory should do what.
for concourse resources the working directory is the only thing that the resource is supposed to interact with
for github actions its GITHUB_WORKSPACE (working dir) RUNNER_TEMP and RUNNER_TOOLCACHE which all have relatively clear mappings
for these its...the whole file system. there's no "standard" where Orbs install tools, etc.
so its pretty unclear how the CLI should expose them, if at all
The text was updated successfully, but these errors were encountered:
No branches or pull requests
forge shape circleci/node@5.1.0/install
would be cool. Thoughts from first iteration:The text was updated successfully, but these errors were encountered: