Skip to content

Commit 9626b64

Browse files
authored
fixing list formatting
1 parent de2fad1 commit 9626b64

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/repos/security/github-advanced-security-code-scanning-troubleshoot.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ Install the CodeQL bundle to the agent tool cache by utilizing the setup script
8787
1. Create an empty file titled `x64.complete` within the `./CodeQL/0.0.0-[codeql-release-bundle-tag]` folder. Using the previous example, the end file path to your `x64.complete` file should be `./CodeQL/0.0.0-codeql-bundle-v2.16.0/x64.complete`.
8888

8989
## How can I explicitly define the repository to publish code scanning alerts to?
90-
1. Use the pipeline environment variable `advancedsecurity.publish.repository.infer: true` to infer the repository to publish from the repository in the working directory.
91-
2. As another option, if you don't explicitly check out a repository or use an alias to check out your repository, utilize the variable `advancedsecurity.publish.repository: $[ convertToJson(resources.repositories['YourRepositoryAlias']) ]`
90+
- Use the pipeline environment variable `advancedsecurity.publish.repository.infer: true` to infer the repository to publish from the repository in the working directory.
91+
- As another option, if you don't explicitly check out a repository or use an alias to check out your repository, utilize the variable `advancedsecurity.publish.repository: $[ convertToJson(resources.repositories['YourRepositoryAlias']) ]`
9292

9393
For more information, check the [release notes](https://learn.microsoft.com/azure/devops/release-notes/2025/ghazdo/sprint-253-update#multi-repository-publishing-scenarios-supported-for-github-advanced-security-for-azure-devops).
9494

0 commit comments

Comments
 (0)