Skip to content
Raw Markdown

Connect a git repository

The GitHub App can validate pull requests and import merged context files automatically. On GitLab, Bitbucket, or another provider, your pipeline runs the equivalent CLI commands.

Before connecting, add the context files to the repository. The configured path, cassis/ by default, represents the complete context.

GitHub

  1. In Cassis, open Settings → GitHub → Connect GitHub.
  2. Install the Cassis App for the repositories it should access.
  3. Select the project and repository, confirm the context path, and save.
  4. Open a test pull request that changes a context file. Cassis should post a cassis / ontology validation check. After merge, the new Cassis version should record the commit.

A merge that touches the context path always creates a new version recording the merged commit, even when the context it brings matches the published one. A push that touches no file under the context path is skipped and creates no version.

On a pull request
The App validates the complete context at that commit.
On the default branch
The App imports the merged tree and publishes a new version.
In your CI
Add the eval suite; the App does not run it for you.

Any other git provider

There is no repository connection to configure in Cassis. Store CASSIS_API_KEY in your CI secrets, then add two jobs:

  • On a pull or merge request, run cassis context check and cassis eval run.
  • On the default branch, run cassis context upload to publish the merged tree.

The CI guide has copy-paste examples for GitHub Actions and GitLab CI.

Use either the GitHub App or a default-branch upload job for a project, not both. They are two ways to publish the same complete context.