Update github-advanced-security-code-scanning-troubleshoot.md

Added FAQ questions for code scanning

Author: omokoh

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

@@ -86,6 +86,13 @@ Install the CodeQL bundle to the agent tool cache by utilizing the setup script
 1.	Download and unzip the bundle to the following directory inside the agent tool directory, typically located under `_work/_tool`: `./CodeQL/0.0.0-[codeql-release-bundle-tag]/x64/`. Using the current release of `v2.16.0`, the folder name would be titled `./CodeQL/0.0.0-codeql-bundle-v2.16.0/x64/`. Learn more about the [agent tool directory](https://github.com/microsoft/azure-pipelines-tool-lib/blob/master/docs/overview.md#tool-cache). 
 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`.
 
+## How can I explicitly define the repository to publish code scanning alerts to?
+1.   Use the pipeline environment variable `advancedsecurity.publish.repository.infer: true` to infer the repository to publish from the repository in the working directory.
+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']) ]` 
+
+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).
+
+
 ## Related articles
 
 - [Set up code scanning](github-advanced-security-code-scanning.md)