Skip to main content

Source control integrations

Link pull requests, commits and pipeline results from GitHub, Bitbucket and GitLab to software change records in Seal.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Source control holds code and configuration, pull or merge requests with their reviews, commits and pipeline results: the evidence of how a software change was made and tested.

EU GMP Annex 11 requires changes to a computerised system, its configuration included, to be made in a controlled way under a defined procedure (Annex 11, 10). For software that supports GxP work, the change record has to show what changed, who reviewed it and what was tested before release.

What Seal reads and writes back.

The Seal Change Control GitHub App creates a Seal change record from a template when a matching pull request opens, and updates it as the pull request changes. It writes back a commit status linking to the record and can approve or close the pull request when the record is approved or rejected; Seal holds the approval, while merge and deployment stay in your delivery workflow. Bitbucket and GitLab are linked through Seal’s API and Scripts, scoped per repository or project.

Seal
  1. BitbucketSource of truth agreed when scoped

    Reads Pull requests, commits and pipeline results

    Writes back If agreed

  2. GitLabSource of truth agreed when scoped

    Reads Merge requests, commits, issues and pipeline results

    Writes back If agreed

  3. GitHubSeal keeps the approval

    Reads Pull requests, as change records

    Writes back Status and approval

3 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo