Run Content Validator in CI

Administration
,
1

Overview

This guide shows how to run the Content Validator as part of CI in Github so pull requests receive a validation check and a comment with any issues. It makes use of a small python utility, Github actions and the Omni API.

What it does

  • Runs the Content Validator API for a model on every PR.
  • Posts a PR comment with validation results (screenshot below).
  • Stores a history artifact to flag new vs existing issues.
  • Supports Omni branches by resolving branch name → branch ID.

omnicles_gh_comment
omnicles_gh_comment1726×1575 162 KB

Demo

Prerequisites

  • Omni API * key with access to the model.
  • Model ID to validate (the MCP server docs describe how to get this)
  • Access to get * Github Actions for your Omni repo.

Setup

  1. Add GitHub 1. secrets and variables:
    • OMNI_API_KEY (secret)
    • OMNI_BASE_URL (variable or secret)
    • OMNI_MODEL_ID (variable or secret)
  2. Run the workflow once on the default branch to create the initial history artifact.
  3. Open a PR to see the check + comment.

Links

Notes

  • The Content Validator API currently validates all content and does not support filters.
  • Optional history helps reduce noise by identifying which issues are newly introduced, use it with the --fail-on-new-only flag (see GH utility README)

Disclaimer

:warning: This is community-built and not an official Omni release. Review the code and use at your own risk.

1 Like