fix(core): fix "repo" scan mode for remote actions #5660
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Before this fix, remote actions (i.e. actions with
source.repository.url
set, not sources declared at the project level) didn't work correctly when using the newrepo
git scanning mode.Also set the default git scanning mode back to
repo
, since this bug (which we've now fixed) was the reason we reverted tosubtree
.The error arose because the base path wasn't being set to the locally cloned path of the remote source's repo early enough in the resolution process. This led to the repo scanning logic using the action's config directory instead of the cloned source directory as the repo root (thus ignoring the sources).
We've added a unit test that verifies that the base path is being set correctly when the action graph is initialized.
Which issue(s) this PR fixes:
Fixes #5625.