A GitHub Action that validates GraphQL schemas against the Nitro registry.
- uses: ChilliCream/nitro-schema-validate@v16
with:
stage: <stage>
api-id: <api-id>
schema-file: ./schema.graphql
api-key: <api-key>
# Optional
comment-mode: none
cloud-url: <cloud-url>| Name | Required | Description |
|---|---|---|
stage |
Yes | The name of the stage |
api-id |
Yes | The ID of the API |
schema-file |
Yes | The path to the graphql file with the schema definition |
api-key |
Yes | API key for authentication |
comment-mode |
No | Pull request feedback mode on failure: comment, review, or none (default) |
cloud-url |
No | The URL of the Nitro registry |
If you self-host Nitro or use a dedicated hosted instance, you can specify the cloud-url input to point to your instance.
Use comment-mode to control pull request feedback behavior.
comment-mode: comment comments on the pull request - requires issues: write permissions
comment-mode: review creates a pull request review with a comment - requires pull-requests: write permissions
Example for comment-mode: comment:
jobs:
validate:
permissions:
contents: read
issues: writeExample for comment-mode: review:
jobs:
validate:
permissions:
contents: read
pull-requests: writeNote: When you define job-level
permissions, GitHub no longer applies the default permission set for that job. Make sure to explicitly include every permission the job needs (for examplecontents: read).