How to Set Up FlexReview Validation

Learn how to enable FlexReview validation in both Aviator and GitHub.

How to Enable FlexReview Validation

FlexReview validation can be enabled in the FlexReview repository-level settings of a specific repo:

Configuring FlexReview.

Validation is enabled at the bottom of the configuration page.

To use FlexReview Validation, add the relevant base branches to your FlexReview repository-level configuration. This ensures that:

• Validation applies only to pull request targeting these specified branches.

• Isolated branches are excluded from Validation.

You can also configure what slack channel break-glass override notifications will be sent to.ˇ

GitHub changes

• When configuring FlexReview Validation, you should move you GitHub Codeowners file to Aviator Owners file to avoid GitHub overriding the validation settings

• In GitHub branch protection rules, make sure the setting “dismiss all approvals on push” is disabled.

• Add Aviator FlexReview as a required check in your branch ruleset:

The "require status checks to pass" option on GitHub's branch rulesets page.

An aviator/flexreview status check in GitHub.

Break-Glass Functionality

In case of emergency merges, FlexReview Validation can be overridden by commenting on the pull request:

Once this comment is posted:

• The PR will only require a single general approval from any user to be merged.

• A Slack notification will be sent to a designated channel to inform the team of the override.