Back to rankings

Windsurf: Devin Checks CI Status for Commits, Branches and Tags

WindsurfView original changelog

Devin can now check CI status for a commit, branch or tag — for example a post-merge run on main — and no longer only for a pull request. The capability works across GitHub, GitLab, Azure DevOps and Bitbucket (both Cloud and Data Center), and Bitbucket build statuses are now visible to Devin on pull requests and commits.

Key Takeaways

  • Devin now reads CI status for a commit, branch or tag, not only for a pull request.
  • The headline case is a post-merge run on main, which a pull-request-only view could not see.
  • Supported across GitHub, GitLab, Azure DevOps and Bitbucket Cloud and Data Center.
  • Bitbucket build statuses are now visible to Devin on pull requests and commits, closing the gap with the other providers.
  • It lets Devin follow a change past merge to the run that actually gates a deploy.
  • Shipped in the Devin release notes dated October 19, 2026.

CI Status Beyond the Pull Request

Devin could already read CI status for a pull request, which covers the normal review loop but stops at the moment a branch is merged. Windsurf's October 19, 2026 release extends that: Devin can now check CI status for a commit, a branch or a tag.

The release notes give the obvious example, a post-merge run on main. That is the case where a failure matters most and where a pull-request-only view was blind: once the pull request is closed, the run that actually gates the deploy is attached to the commit or the branch, not to the pull request.

Supported Providers

The capability is not limited to one forge. Devin can read these statuses on:

  • GitHub
  • GitLab
  • Azure DevOps
  • Bitbucket, on both Cloud and Data Center

Bitbucket Build Statuses Now Visible

Alongside the broader lookup, Bitbucket build statuses are now visible to Devin on pull requests and commits. Bitbucket users previously had the thinnest view of the four providers, so this closes that gap and brings Bitbucket in line with the others.

Why It Matters

An agent that can only see pull-request checks can confirm that a change looked green before merge, but it cannot tell whether the change is actually healthy afterward. Reading status per commit, branch or tag lets Devin follow a change through to the run that matters, and it makes post-merge failures something Devin can notice and act on rather than something a human has to bring to it.