microsoft / microsoft/sarif-web-component
Branch data from versionControlProvenance is not processed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 108
- Forks
- 36
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 3
Description
On Azure DevOps the links from scan tab after running pipeline to the files from repo do not contain branch data and provide to the last chosen repository.
The versionControlProvenance is filled in the following way:
"versionControlProvenance": [{
"repositoryUri": "https://dev.azure.com/xtest-devel/example/_git/example",
"branch": "refs/heads/main",
"mappedTo": {
"uriBaseId": "ROOT_1_main"
}
}
],
The locatins part from results is filled in the following way:
"results": [{
"locations": [{
"physicalLocation": {
"artifactLocation": {
"uri": "demo/src/main/java/examples/nbank/Customer.java",
"uriBaseId": "ROOT_1_main"
},
"region": {
"startLine": 89,
"startColumn": 41,
"endColumn": 42
}
}
}
]
}]
Scan tabs looks like on the screenshot
The produced link for demo/src/main/java/examples/nbank/Customer.java is like this:
https://dev.azure.com/devel/example/_git/example?path=demo%2Fsrc%2Fmain%2Fjava%2Fexamples%2Fnbank%2FCustomer.java
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the scan tab consumes versionControlProvenance and locations.uriBaseId when constructing Azure DevOps links. Use the provided repositoryUri, branch, and generated Customer.java URL as the reproduction case; done means the link includes the branch data and targets the selected repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100