Bitbucket Cloud

Revue works with bitbucket.org (Bitbucket Cloud). You can use it without a GitHub account, and connect several Bitbucket accounts.

Sign in#

1. On the welcome screen click Bitbucket Cloud, or in Settings → Accounts click Add Bitbucket account.
2. Click Sign in with Bitbucket. A tab opens on bitbucket.org.
3. Sign in there if it asks, then click Grant access.
4. Come back to Revue and pick the workspaces to watch (see below).
5. Click Connect Bitbucket.

Guide: Sign in with an API token#

1. Click Advanced: use a token instead under Sign in with Bitbucket.
2. Click Create token. Atlassian's API tokens page opens.
3. Create an API token for Bitbucket with the scopes below, and copy it.
4. In Revue, type your Atlassian account email and paste the token.
5. Click Connect Bitbucket, then pick the workspaces to watch.

Each scope in the form has a copy button, so you can paste the names into Atlassian's page.

Watched workspaces#

Bitbucket can't search pull requests across repositories. So Revue looks in the repositories of the workspaces you choose to watch:

• To review and All in my repos cover the most recently updated repositories of the watched workspaces.
• Mine (your own pull requests) is found in all your workspaces, watched or not.

When you sign in, Revue lists your workspaces and ticks them all. Untick the ones you don't review in.

To change them later, open Settings → Accounts and click Workspaces… under the account. The line there says which ones it watches, or Watching no workspaces: the repositories of your own open PRs.

Advanced: how many repositories are covered

• The pull request list shows the latest open pull requests of the 15 most recently updated repositories of the watched workspaces, plus your own open pull requests in any workspace.
• Searching the list for older or closed pull requests reaches up to 30 of those repositories, most recently updated first.
• Ctrl+K search asks up to 15 repositories Revue knows, besides your own pull requests.
• Repositories you ignore (see Settings reference) leave room for others.
• With no workspace watched, Revue uses the repositories of your own open pull requests.
• If Revue can't list your workspaces (the token lacks read:workspace:bitbucket), it says so and you type the workspace IDs instead, comma separated. A workspace link or a repository link (bitbucket.org/ws/repo) works too.

Each repository costs Bitbucket a request, which is why the counts are capped.

What's different on Bitbucket#

Most of Revue works the same as on GitHub. A few things work differently, because of what Bitbucket offers:

• Submitting a review posts its comments one by one, then your summary as a plain comment, then the approval or change request. If one fails, the comments already posted leave your drafts and the rest stay drafts, so you can submit again.
• Viewed marks on files stay in Revue (Bitbucket has no way to store them).
• No reactions: Bitbucket has none.
• Editing a pull request covers its title, description, base branch, draft state and reviewers. Bitbucket has no assignees, labels or milestones.
• No check logs: build statuses show, but their logs can't be opened in Revue.
• Pull requests from forks work: their commits are read from the fork.

Browsing code with a browser sign-in#

Bitbucket only accepts browser (OAuth) sign-ins on its API, not for downloading a repository at once. So for an account signed in with the browser, the Code tab fetches a commit's files one by one, for repositories of up to 2000 files. Large non-text files are left out.

For a larger repository, Revue says it has too many files to fetch one by one. To browse its code, sign the account in with an API token instead (Settings → Accounts). See Browsing code.

Links Revue understands#

• https://bitbucket.org/workspace/repo/pull-requests/12

Paste it into Ctrl+K (Cmd+K on macOS), or open it with revue <link>. See Links and opening from anywhere.

Troubleshooting: Bitbucket is slow or refuses requests

Bitbucket allows about a thousand API requests an hour. When it answers "too many requests" (429), Revue waits as long as Bitbucket asks. When it's overloaded (502, 503, 504), Revue retries what you asked for a couple of times, and pauses background refreshes for a few minutes (2, then 4, then 8) instead of asking again every cycle.

The status bar's API requests left shows each account's allowance, when the service reports one.

Jira with Bitbucket#

Bitbucket and Jira usually share one Atlassian account. When you connect Jira after Bitbucket, Revue fills in the same email for you. See Jira.