Skip to main content

​
What Are Gates?

Gates are merge requirements for a Trail. They bring branch freshness, human review, agent findings, and CI checks into one place so your team can see what is satisfied, pending, or blocking a merge. While Runners produce automated evaluations, Gates apply your repository’s merge policy to the relevant evidence, including unresolved review findings and check results.

​
Configure Gates

With repository admin permission:
  1. Open your repository in entire.com.
  2. Select Settings then Gates.
  3. Turn on Enable gates.
  4. Enable the Gates that you need for your repository.
  5. Configure the requirements for each enabled gate.
  6. Choose who may bypass a blocking gate.
Start with the requirements your team already uses for pull requests. Set up and merge the trail-review runner before making Agent review blocking.

​
Up to Date

This gate checks whether the Trail’s branch is current with its base branch. You need to configure whether to allow a clean merge when the branch is behind. Use a blocking requirement when your team needs changes evaluated against the latest base before merging.

​
Human Review

This gate evaluates approvals submitted on the Trail. Configure:
  • The minimum number of approvals.
  • Whether the Trail author’s approval counts.
  • Whether new pushes reset existing approvals.
For example, require one approval, exclude the author, and reset approvals after a push when changes should receive a fresh review.

​
Agent Review

This gate evaluates unresolved runner findings on the latest push. The default trail-review runner produces findings with high, medium, or low severity. Choose the severity threshold that matches your team’s merge policy. Review each blocking finding and fix, resolve, or dismiss it. After a new push, findings tied to older code may become stale. Current findings remain open until they are resolved or dismissed.

​
Checks

This gate evaluates CI checks reported through GitHub. Choose either:
  • The checks GitHub marks as required.
  • Specific check names you want to require.
Trails currently use a backing GitHub pull request for CI. Configure the checks your team needs before merging, such as its existing test and build checks.

​
Review Gate Status on a Trail

Open the Trail’s Gates section to see which requirements have passed and which are pending or blocking. Address the underlying requirement: update the branch, get an approval, handle findings, or investigate failing CI checks. Select Approve when your review is complete. Once all blocking gates pass, select Merge. If a blocking gate needs to be bypassed, only a person permitted by the repository’s bypass configuration can do so. Every bypass is recorded on the Trail.