iris gate as your quality gate step. No browser, no interactive login, no persistent state on the runner.
Exit codes
Use exit codes to control pipeline behaviour.iris gate follows the same conventions as all other Iris commands:
| Exit code | Meaning | Pipeline action |
|---|---|---|
0 | All files pass the threshold | Pipeline continues |
1 | One or more files below threshold | Fail the build |
2 | Bad arguments or invalid config | Fix the workflow step |
Setting IRIS_LICENCE_TOKEN
Add your licence key as a secret in your CI provider settings, then expose it as theIRIS_LICENCE_TOKEN environment variable in the step that runs Iris. The CLI checks this variable before reading the credentials file, so no iris auth login step is needed on runners.
iris secrets runs without any authentication at all. Use it for a free CI scan that requires no licence — it works on any runner regardless of IRIS_LICENCE_TOKEN.GitHub Actions
The example below shows a minimaliris gate step. For the full workflow including branch protection rules and threshold configuration, see the GitHub Actions guide.
For inline PR annotations, use
iris gate . --format github (added in v1.6.0). See the full guide at /enforcement/github-actions.