GitHub Action

Run Schema Gateway on every pull request.

The free action turns structured-output portability into a visible CI artifact: lint one schema across provider targets, compare baseline versus candidate when you have both, and publish a job summary with the first generated request fragment before the merge lands.

PR gate provider portability becomes reviewable in CI
Regression signal baseline-versus-candidate verdict when you have both schemas
Generated fragment the first provider request body is written into the artifact 
name: Schema portability

on:
  pull_request:
  push:
    branches: [main]

jobs:
  check-schema:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: sravan27/schema-gateway/.github/actions/portability-check@v0.1.3
        with:
          baseline-schema: schema.prev.json
          schema: schema.json
          targets: openai,gemini,anthropic,ollama
View action source Run regression demo See compiler output
Action boundary
What goes in and what comes back out
Input One schema path, optional baseline schema path, and a target list such as openai,gemini,anthropic,ollama.
Evaluation Schema portability linting plus baseline-versus-candidate regression detection when both versions are available.
Artifact A CI summary with compatibility status, top issue codes, regression verdict, and the first generated provider snippet.
Upgrade path Stay on the free action locally and in CI, then move to Starter Access only when you want one signed hosted origin for shared workflows.
Generated fragment
The summary does not stop at pass or fail
openai.responses_api

Reviewers see the first provider request fragment directly in CI, which makes provider-specific drift easier to discuss during review.

openai.responses_api
{
  "text": {
    "format": {
      "type": "json_schema",
      "strict": true
    }
  }
}