ChatPilot
Integrations

Bitbucket

See your Bitbucket pull requests as chats in the inbox and answer their comments from ChatPilot.

ChatPilot can show your Bitbucket pull requests as chats, next to your mail and messages. It works with Bitbucket Cloud (bitbucket.org).

Add your e-mail and token

  1. Go to your Atlassian account (id.atlassian.com) → Security → Create and manage API tokens → Create API token with scopes. Give it a name and an end date, pick the app Bitbucket and the scopes read:user, read:workspace, read:repository, read:pullrequest and write:pullrequest (ChatPilot reads your pull requests and posts the comments you send), then copy the token. For failed pipelines under Build and error signals, add read:pipeline.
  2. In ChatPilot, open Settings → Integrations, click the Built in row at the bottom, then Bitbucket.
  3. Fill in your Atlassian account e-mail (the one you sign in to Bitbucket with) and paste the token under API token, then click Check and save. ChatPilot tries them on Bitbucket and shows whose they are.

An older Bitbucket app password works too: fill in your Bitbucket username instead of the e-mail.

The e-mail and token are kept together in the Keychain on this computer only. Remove token deletes them here; to revoke the token at Atlassian too, delete it under API tokens there.

Pull requests in the inbox

On the same page, switch on Pull requests in the inbox. Every open pull request you wrote or are a reviewer on, and that was active in the last 30 days, shows up as a chat under Bitbucket in the inbox list of apps (once one of them is switched on). A pull request is written repository#12 PR, as on Bitbucket.

Bitbucket can't list everything you take part in at once, so ChatPilot looks in the 30 repositories you're a member of that changed most recently. To choose them yourself, click Which repositories under the switch. It lists the repositories you're a member of and the ones already in the inbox; tick the ones you want, or type another one as workspace/name under Another repository. Tick none to go back to the 30 most recent. Only pull requests active in the last (days) sets how far back it looks (30 at first). Click Save: ChatPilot looks again at once. Chats of a repository you take out stay, with their switches; they just get no new comments.

Like every chat they start switched off: switch Index on for the ones ChatPilot may read, and AI for the ones it may sort and draft for. The pull request's title and description are the first message and each comment a message after it. A comment on a line of code starts with the file and line, and approvals and requests for changes show as Approved and Asked for changes. Your reply is posted as a comment, only when you send it; when you answer a comment, the reply goes under that comment. ChatPilot looks for new comments every five minutes.

A pull request chat joins a project by itself when its repository is listed there.

Bitbucket's notification mails about a pull request whose chat is switched on don't come in as new mail any more: its comments already come into the Bitbucket chat, so the mail is kept in its mailbox as read — no alert, not sorted. The Bitbucket chat says how many such mails there are, and Show the mails opens them. Mails about pull requests whose chat is off stay ordinary mail. Only mails from Bitbucket's own notification address count; their text isn't copied into the Bitbucket chat.

For now a reply is text only (add files on Bitbucket itself).

Checked against ChatPilot 0.1.0b6. Report a problem with this page