Skip to main content
A gate is the pass or fail decision Iris Code makes by comparing your code with your project’s minimum standards. Before you start stopping pushes or builds, it helps to know how the code would do today. Gate Preview shows whether the current project would pass, and which limits it would fail, without blocking anything. Use it to pick settings your team can actually meet before you enforce them.

Opening it

Open Improve and choose the gate preview. You can also open Preview Gate from the File tab. If you select a saved project scan, the preview uses that saved result. It shows which files the scan covered and when it was taken, and it does not rescan your code or use another project action. A project action is one unit of the monthly allowance that folder and workspace scans use; see Free project actions. Without a saved result, the basic preview checks the current workspace against the presets, skipping any files in your ignoreFiles list.

The six presets

A preset is a ready-made set of limits. They are listed here from most lenient to most strict:

What the preview shows

  • Scan average: one score across the files in the displayed scope
  • Files analysed: how many files were included
  • Threshold card: which presets you already pass, and the next one you would fail
  • Recommendation: the strictest preset you could adopt today without anything being blocked
  • Focus card: one preset in detail, with controls to step through the others and an Apply button
  • Preset grid: all six at a glance, each clickable
The focus card shows the preset, its minimum score and how many files fail. It also lists those files with their details when you are looking at a saved scan result or have Pro. Apply writes presetId into .irisconfig.json for you, without opening the file.

Free and Pro

The preview is Free. Opening the file details of a scan you have already run does not use another action. Stopping code at a push, a build or a CI run needs paid access. A preview on its own does not install a hook or prevent a push. An earned scan is a project scan you have already run and can reopen at no further cost.

Acting on the results

On Free, add "presetId": "balanced" (or whichever preset you chose) to .irisconfig.json. Everyone on the team then gets the same results from the same limits. Nothing is blocked yet, but the standard is agreed and committed. On Pro, install the git hook or the build gate to start stopping files that score below your chosen threshold. If many files fail, start at legacy or balanced and tighten over time rather than jumping to the strictest preset. A gate that fails all the time tends to get switched off.
Gate Preview never writes config or blocks anything on its own. Applying a preset is the only action that changes a file, and only when you click Apply.