New Feature: ChatOps in Pull Requests Now Available for GitLab, Azure DevOps, and Bitbucket

Arnica’s ChatOps in Pull Requests feature has just leveled up.

What began as support for GitHub now includes GitLab, Azure DevOps (ADO), and Bitbucket, making it easier than ever for teams across the major version control platforms to manage security risks directly within their pull request workflows – all viaChatOps

With this update, Arnica brings real-time, in-context alerting and response to developers and reviewers where they already work, no extra tools or context switching required.

🆕 What’s New and Why it Matters

Arnica now supports all four major source code management platforms - GitHub, GitLab, Azure DevOps, and Bitbucket, extending the reach of a key capability to enterprises and complex organizations that rely on multiple platforms. This expansion helps unify risk management workflows natively for developers across diverse environments.

Managing code risks is often hindered by delays or a lack of context. Developers may receive alerts too late, and security reviewers might not see them at all or cause unnecessary friction.  Arnica addresses these challenges by embedding ChatOps directly into pull request conversations, surfacing actionable alerts where developers and reviewers are already working.

It is worth mentioning that developers typically interact with ChatOps over Slack/Teams upon pushing the code to a feature branch, before the pull request is opened. And now, when Arnica detects a policy-based risk, it automatically posts a detailed comment on the pull request. This comment includes built-in actions like:

These actions can be taken immediately, without leaving the pull request, enabling real-time collaboration and reducing friction between development and security workflows. This approach ensures developers can stay in their flow, reviewers are looped in at the right moment, and teams resolve risks faster and with greater confidence.

For organizations that require more oversight, Arnica allows administrators to configure workflows that require review for alert dismissals, adding an optional governance layer that aligns with internal policies.

👥 Roles That Benefit from ChatOps in PRs

This enhancement is designed to support a wider range of roles across your development and security teams for a variety of organizations using one or more of the major source code management platforms.

• Developers benefit by being able to resolve issues quickly without disrupting their workflow. This allows them to stay focused on building and delivering features, while still addressing security concerns efficiently.
• Reviewers gain valuable insight into unresolved risks, enabling them to contribute directly to risk mitigation. They can better understand the context of changes and provide more meaningful feedback that improves overall code quality and security posture.
• Application Security teams see faster adoption of security practices, as developers can use familiar workflows without needing to be trained on entirely new tools. This accelerates security integration across the development lifecycle and reduces resistance to adoption.

Stakeholders such as security and legal, even when operating in read-only roles, can actively participate in the process. They do not need direct access to the codebase to stay informed or offer guidance, making collaboration easier and more inclusive across the organization.

🛠️ How to Enable ChatOps in Your Pull Requests

ChatOps in PRs is available now for GitHub, GitLab, ADO, and Bitbucket. If your repos are already connected to Arnica, you can turn it on in your project settings today. This update brings even more flexibility to your security workflows—no matter what platform you use. Let developers stay focused, let reviewers stay informed, and let security scale across the board.

‍