[Bug]: Action scan misbehaviour?

[stefreak]

Bug

Current behavior

• This causes scan of entire repository:
  • Running an action declared in a subdirectory of the root project scans entire repository (garden run subdir -l4)
  • Running an action declared in a subdirectory of a subproject scans entire repository ((cd subproject; garden run subproj-subdir -l4))
  • Running an action declared at the root of a subproject scans entire repository ((cd subproject; garden run subproj -l4))
• Also, it's possible to run actions that are declared in subprojects from the root project (e.g. garden run subproj)

Expected behavior

• Only the subproject should be scanned in the following cases:
  • Running an action declared in a subdirectory of the root project (garden run subdir -l4)
  • Running an action declared in a subdirectory of a subproject ((cd subproject; garden run subproj-subdir -l4))
  • Running an action declared at the root of a subproject ((cd subproject; garden run subproj -l4))
• It shouldn't be possible to run actions that are declared in subprojects from the root project (e.g. garden run subproj); Is it a feature or a bug though?

Reproducible example

scan-repro.tar.gz

Workaround

Unknown

Suggested solution(s)

Scan only necessary directories before actually running an action

Additional context

This behaviour also exists in older 0.13 versions, so it's not a recent regression.

Your environment

• OS: MacOS

0.13.34