{
  "id": 7683356,
  "title": "Reviewing AI-generated code on GitLab and Azure DevOps: what actually exists",
  "url": "https://urgent.news/2026/09/16/reviewing-ai-generated-code-on-gitlab-and-azure-devops-what-actually",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-16T02:15:01.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/emilreiter/reviewing-ai-generated-code-on-gitlab-and-azure-devops-what-actually-exists-3mi8"
  },
  "original_language": "en",
  "account": "When searching for ways to identify low-quality AI-generated pull requests, the primary tool mentioned is CodeRabbit Slop Detection. However, this tool is specifically designed for GitHub repositories and is only available on the Essentials plan. The search yielded limited information on AI-generated code review tools for GitLab and Azure DevOps, even on their self-managed editions. Neither GitLab nor Azure DevOps currently offer a native feature that explicitly marks a merge request as AI-authored. The documentation does not support any such flag. However, both platforms support the same quality and security standards for AI-generated code. SonarQube Server, a self-managed solution, directly addresses AI-generated code by applying automated code review in the CI/CD pipeline. This review process checks for bugs, vulnerabilities, and maintainability issues, with quality gates that prevent failing code from merging. The SonarQube Server documentation states that all new code, whether authored by developers or generated by AI agents, must meet the same standards. This approach applies the same ruleset to every pull request and gates on the outcome, effectively catching low-quality PRs regardless of their origin. Currently, there is no tool that can accurately determine the percentage of a PR that was machine-written, as such a feature is not documented on GitLab or Azure DevOps. Additionally, the availability of AI-specific features within SonarQube, including those related to AI code assurance, is dependent on license and edition, and verification of these limits was not conducted during the research. It is important to note that the absence of a documented AI-authored flag on a platform does not mean that such a feature will never exist. However, building review policies based on undocumented features can lead to teams making unverified assumptions.",
  "summary": "When you look for a way to catch low-quality AI-generated pull requests, the tool everyone names is CodeRabbit Slop Detection. Read its own docs and you get one line that settles the whole question: \"On GitHub repositories.\" GitHub-only. The SERP is thin on the non-GitHub forges and the feature itself sits behind an early-access footnote on the Essentials plan. So what do you actually run for…",
  "key_points": [
    "CodeRabbit Slop Detection tool for GitHub only, not GitLab/Azure DevOps.",
    "GitLab/Azure DevOps lack native AI-authored code flags in documentation.",
    "SonarQube Server applies same quality standards to AI-generated code."
  ],
  "editors_take": "The lack of native AI-generated code marking on GitLab and Azure DevOps means teams must rely on third-party tools like SonarQube Server to enforce quality standards for all code, regardless of origin.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}