Git hosting integrations

Riff connects to the places your code already lives: Azure DevOps, GitHub, GitLab and Bitbucket, including self-hosted and enterprise instances.

Connect a host

  1. Open the integrations area in Riff.
  2. Pick your provider: Azure DevOps, GitHub, GitLab or Bitbucket.
  3. For a self-hosted or enterprise instance, point the connection at your own server.
  4. Authorize the connection with your provider account.

The Free plan includes 1 host connection; Pro raises that to 4. The Repository Management home tab shows the health of every connection at a glance, so a broken integration is visible before it surprises you mid-task.

Browse and batch clone

Once a host is connected, you do not have to clone repositories one at a time:

  1. Browse the repositories your account can reach on the connected host.
  2. Select one or several.
  3. Clone them in a single batch.

This is the fastest way to set up a new machine or onboard onto a team with many repositories. Pair it with workspaces to keep the result organized. See Workspaces and repositories.

Pull requests

Riff brings pull requests into the client:

  • List the pull requests of a repository and read their diffs inline, without switching to the browser.
  • Create pull requests with your team's PR template applied, so descriptions start from an agreed structure. See Commit and branch templates.
  • Across every repo and provider, Setlist gathers the pull requests that need your review and the ones waiting on others, with snooze and saved views.

SSH keys

Riff includes SSH key management, so you can set up key-based access to your hosts without leaving the client.

One engine underneath

Whatever the host, Riff drives the real Git CLI installed on your machine. Clone, fetch, push and pull behave exactly like your terminal, and force-push always uses --force-with-lease. See Undo, redo and the safety net for everything that protects those operations.