GitLab, without opening GitLab.
Read-only GitLab: merge requests and their reviews, issues, pipelines down to the failing job's log.
In your channel
Ask Ray for something in GitLab 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 GitLab
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 GitLab
- List all project members
- List project users
- Get current user
- Get issue
- Get job details
- Get job trace
- Get merge request notes
- Get project
- Get projects
- Get projects id merge requests iid diffs
- Get project merge request
- Get project merge requests
- Get project merge request commits
- Get raw file
- Get repository branches
- Get single commit
- Get single pipeline
- List group projects
- List issue notes
- List labels
- List merge requests
- List milestones
- List pipeline jobs
- List project issues
- List project pipelines
- List repository commits
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Move GitLab issue to another project
- Edit a GitLab issue comment
- Update GitLab merge request
- Comment on GitLab issue
- Open a GitLab merge request
- File a GitLab issue
- Update GitLab issue
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 group
- Archive project
- Validate credential
- Delete issue note
- Cancel job
How Ray works with GitLab
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect GitLab
One click, right where you asked. Ray posts a connect card, you authorise GitLab 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 GitLab, and tell Dana it is being looked at.
Move GitLab issue to another project
- Waiting on
- your approval
What does connecting GitLab to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect GitLab and it can do the GitLab 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 GitLab account, so Ray can only reach what that person can already reach, and the history in GitLab shows who actually asked.
Security and permissions
- You authorise GitLab 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 GitLab 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 GitLab.
Free to start, no credit card, and it asks before it acts.