Offer: Virgo is available for free to use within your infrastructure. Book a demo

Bitbucket

The Bitbucket connector brings workspaces, repositories, pull requests, commits, and comments into the graph. It stays current through a webhook.

Entities

Entity	Represents	Key fields
`bitbucket_workspace`	A workspace	`slug`, `name`
`bitbucket_repository`	A repository	`full_name`, `description`, `main_branch`
`bitbucket_user`	A person	`account_id` (id), `display_name`, `email`
`bitbucket_commit`	A commit	`hash` (id), `message`
`bitbucket_pull_request`	A pull request (aliases PR, MR)	`title`, `status`, `source_branch`, `destination_branch`
`bitbucket_comment`	A pull request comment	`body`, `path`

Relationships

Relation	Target
`owner`	`bitbucket_workspace`
`authored_by`, `reviewed_by`, `commented_by`	`bitbucket_user`
`in_repository`	`bitbucket_repository`
`has_commit`	`bitbucket_commit`
`has_comment`	`bitbucket_comment`
`on_pr`	`bitbucket_pull_request`

Exposing for linking

Bitbucket exposes two entities so other sources can reference them:

bitbucket_pull_request is recognized from pr#123, pull request #123, or a pull-request URL.
bitbucket_commit is recognized from a full or short commit hash, or a commit URL.

See Cross-domain linking.

Connector framework: how a connector like this is defined.
Entities and Retrievers.