Running forge from a subdirectory will re-clone services

[tristanpemble]

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

[rhs]

This should be fixed in 0.3.21