“@Ray open an issue on the api repo about the timeout.”
What Ray can do in GitHub
Reading is free, because reading changes nothing. Everything that writes waits for you, and the rest is not connected at all.
Reads freely
Looks things up on its own
- Issues and their comments
- Repositories your connection covers
Asks first, every time
Waits for your approval
- Create an issue
- Comment on an 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.
Never
Not wired at all
- Push code, open pull requests, or merge anything
- Delete an issue or a comment
These actions are excluded from the toolset Ray is given, so they are not something it could do and chooses not to.
Connecting it takes one click
Ask Ray for something in GitHub and it posts a Connect button in the thread. The link opens GitHub’s own login screen, so your credentials go to them and never through us. Ray picks up the task it was already working on as soon as you are back.
The connection belongs to your workspace. Uninstall Ray and it is revoked, along with everything else it was holding.
The rest of the set
- LinearFile properly written issues from a conversation, and keep their status honest.
- JiraThe same ticket craft, in the tracker your company already runs on.
- AsanaCapture work as tasks in the project it belongs to.
- ClickUpSame job, in ClickUp's lists and spaces.
- GmailDraft the follow-up in your voice. Sending is the one thing it always asks about.
Put Ray to work in GitHub.
Free to start, no credit card, and it asks before it acts.