SonarQube

• Quality gate fails or changesRuns when an analysis leaves a project's quality gate failed (or passed again, or changed either way), with the conditions that failed. It runs once per change, so a gate that stays failed doesn't run it again.
• New issueRuns for each new open issue an analysis finds, oldest first, such as each high-severity security issue, up to 50 a look. Issues found before the workflow is turned on don't run it.
• New analysisRuns when SonarQube finishes analysing a project (or one of its branches), oldest first, with the quality gate status it got. Analyses before the workflow is turned on don't run it.

• List projectsFind the projects the token can browse, by name or key, with whether each passes its quality gate, such as every project failing its gate.
• Get projectGet a project's name, tags, visibility, version, when it was last analysed and its quality gate status.
• Create projectCreate an empty project, ready for its first analysis, such as one for each new repository. The token's user needs the Create Projects permission.
• Delete projectDelete a project with all its analyses, issues and measures. This can't be undone. The token's user needs Administer on the project.
• Set project tagsAdd, remove or replace a project's tags, such as the team that owns it. The token's user needs Administer on the project.
• List branchesList a project's analysed branches, the main one first, with each one's quality gate status and last analysis.
• Get quality gate statusCheck whether a project, branch or pull request passes its quality gate, with the conditions that failed, such as before a release.
• Get project's quality gateFind out which quality gate a project uses, and whether it is the default one.
• Set project's quality gateMake a project use a quality gate, such as a stricter one for a service handling payments. The token's user needs Administer on the project.
• Remove project's quality gateStop a project using its own quality gate, so it goes back to the default one. The token's user needs Administer on the project.
• Get project measuresGet a project's measures: coverage, issues by software quality, bugs, vulnerabilities, code smells, duplications, ratings and technical debt, overall and on new code, for a weekly report or a check.
• Search issuesFind issues by project, branch, severity, software quality, status, assignee, tag, rule or when they were found, such as every open high-severity security issue. Get them as a list and as text for an AI step or a message.
• Assign issueAssign an issue to someone, or leave it unassigned.
• Change issue statusAccept an issue (it stays, on purpose), mark it a false positive, or reopen it, with an optional comment saying why. Accepting and false positive need the Administer Issues permission.
• Set issue severityChange how severe an issue is, such as raising one a team must fix before release. Needs the Administer Issues permission.
• Set issue tagsAdd, remove or replace an issue's tags, such as triage or a team's name.
• Add issue commentComment on an issue, such as a link to the ticket it was filed as.
• List security hotspotsList a project's security hotspots (code to review for security) to review or already reviewed. SonarQube 2026.4 and later raise security issues instead, which Search issues finds.
• Review security hotspotMark a security hotspot reviewed: fixed, safe, or acknowledged (a real risk left as it is), with a comment. Needs the Administer Security Hotspots permission.
• List analysesList a project's analyses, newest first, with what changed at each: the quality gate passing or failing, a new version, and more.

No actions match that.