Open wooch82 opened 11 months ago
This is tricky. The viewer constructs those URLs from the "version control provenance" object it receives, which (if it doesn't exist) this extension defaults to the repository that the build is linked to, not necessarily the repo that the results are from. So that seems to point to two things that need doing:
Regarding documentation each repo is checked out to a custom path $(Pipeline.Workspace)/s/RepoName if use multi-checkouts. In scans result section filenames have wrong links with RepoName
so it causes the error I try to see the file in a repo: