Bitbucket, without opening Bitbucket.
Read-only Bitbucket: pull requests and review activity, issues, commits, pipeline and deployment state.
In your channel
Ask Ray for something in Bitbucket and it posts this card in the thread. One click, and the task you asked for carries on where it left off.
What Ray can and cannot do in Bitbucket
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in Bitbucket
- List workspace members
- Get commit diff
- Get current user2
- Get file from repository
- Get pull request
- Get pull request commits
- Get pull request diff
- Get pull request diffstat
- Get repositories commit
- Get repositories pipelines steps
- Get repositories pullrequests activity
- Get repositories pullrequests comments
- Get repositories pullrequests statuses
- Get repository
- Get workspaces pullrequests
- Get workspaces search code
- List branches
- List commits
- List deployments
- List issues
- List pipelines
- List pull requests
- List repositories in workspace
- List workspaces
- List workspace projects
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Update Bitbucket pull request
- Update Bitbucket issue
- File a Bitbucket issue
- Comment on Bitbucket issue
- Open a Bitbucket pull request
- Comment on Bitbucket pull request
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete commit comment
- Delete issue
- Delete pull request comment
How Ray works with Bitbucket
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Bitbucket
One click, right where you asked. Ray posts a connect card, you authorise Bitbucket with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Bitbucket, and tell Dana it is being looked at.
Update Bitbucket pull request
- Waiting on
- your approval
What does connecting Bitbucket to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Bitbucket and it can do the Bitbucket part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Bitbucket account, so Ray can only reach what that person can already reach, and the history in Bitbucket shows who actually asked.
Security and permissions
- You authorise Bitbucket on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Bitbucket in a message, or uninstall Ray and every connection it held is revoked.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Bitbucket.
Free to start, no credit card, and it asks before it acts.