Bitbucket, without opening Bitbucket.
The same review work, in Bitbucket, with the pipeline state alongside it.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Bitbucket details, and Ray takes it from there.
@Ray what is still open on the payments pull request?
@Ray open a pull request from the fix branch and describe what changed.
@Ray which pull requests have been waiting on review since last week?
@Ray comment on that pull request asking for a test on the null case.
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.
28 reads wired, 6 actions that wait for a human.
Runs on its own
What Ray reads in Bitbucket
- Pull requests, their diffs, comments, and review activity
- Issues, commits, branches, and repository files
- Pipelines, deployments, and commit statuses
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- File an issue
- Update an issue
- Open a pull request
- Update a pull request
- Comment on an issue or a 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.
- Merge a pull request
- Create a branch, a commit, or a repository
- Delete an issue, a comment, or a repository
- Change pipeline configuration variables
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Bitbucket actions Ray can take, each one stopping in the thread with the real content before it happens.
- 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
Update Bitbucket pull request
Showing Pull request id, each carrying the exact content that will land.
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
Ray uses Bitbucket together with the rest of your tools.
One ask can read Bitbucket, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
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.
Bitbucket and Ray, answered
The questions teams ask before they connect Bitbucket. Every answer is how this integration is built rather than a promise about it.
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.