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
demonstration:
λ tree . ├── README.md ├── forge.yaml ├── k8s ├── service.yaml └── workspace └── customer-portal ├── Dockerfile ├── k8s │ └── deployment.yaml └── service.yaml 4 directories, 6 files λ forge pull ║ [.forge/message-broker] git pull ║ Already up-to-date. ║ [workspace/customer-portal] git pull ║ Already up-to-date. ║ [.forge/admin-portal] git pull ║ Already up-to-date. ║ [.forge/payment-processor] git pull ║ Already up-to-date. ║ git pull ║ Already up-to-date. ║ 42 tasks run, 0 errors ║ λ cd workspace/customer-portal λ forge pull ║ cloning git@github.com:forge-playground/payment-processor.git->.forge/payment-processor ║ cloning git@github.com:forge-playground/message-broker.git->.forge/message-broker ║ git pull ║ Already up-to-date. ║ [.forge/payment-processor] git pull ║ Already up-to-date. ║ [.forge/message-broker] git pull ║ Already up-to-date. ║ 41 tasks run, 0 errors ║
I was expecting the second forge pull to use the services in ../../.forge
forge pull
../../.forge
The text was updated successfully, but these errors were encountered:
This should be fixed in 0.3.21
Sorry, something went wrong.
No branches or pull requests
demonstration:
I was expecting the second
forge pull
to use the services in../../.forge
The text was updated successfully, but these errors were encountered: