analysis-issueslisted

# Rules-Based Analysis Issues When tasked with triaging or clearing rules-based analysis issues (bugs, vulnerabilities, code smells) for a repository, follow this workflow. ## Step 1: Gather Repository Information Determine the `repositoryName` and `branchName`: **`repositoryName`** — the repository name in `owner/repo-name` format (e.g., `organisation/my-project`). The server is case-insensitive and handles `.git` suffixes automatically. **`analysisName`** *(optional)* — if the repository is a mono-repo with multiple analysis projects, provide the analysis project name to disambiguate. Case-insensitive. Leave empty for single-project repositories. If omitted and multiple projects are found, the server returns an error listing the available analysis names. **`branchName`** — run this shell command: ```bash git branch --show-current ``` This returns the `branchName` (e.g., `main`, `develop`, `feature/login-page`). **`pullRequest`** *(optional)* — to retrieve the issues raised on a pull request's new code instead of the whole branch, supply the PR number. Resolve it for the current branch using **standard git only** — no GitHub/Azure/Bitbucket CLI required. Every major host advertises the PR as a ref whose head equals the source-branch tip, so match the branch's remote head SHA against those refs: ```bash BRANCH=$(git branch --show-current) SHA=$(git ls-remote origin "refs/heads/$BRANCH" | cut -f1) git ls-remote origin "refs/pull/*/head" "refs/merge-requests/*/head" "r