Read-Only Mode in FlexReview
Learn how the read-only more works in FlexReview and get use instructions. This mode allows you to test out FlexReview without interfering with any workflows.
Last updated
Was this helpful?
Learn how the read-only more works in FlexReview and get use instructions. This mode allows you to test out FlexReview without interfering with any workflows.
Last updated
Was this helpful?
FlexReview's read-only mode allows you to test out FlexReview without interfering with any workflows.
When you install the Aviator app and enable FlexReview, it starts in read-only mode, that is, it won’t take any actions or post any comments on the PRs automatically.
When in read-only mode, you can use to get suggestions and status checks, or use the web dashboard for the same. FlexReview will not publish any comments automatically.
To turn off read-only mode, activate FlexReview for one or more teams. You can do that directly from the by selecting the team in the dropdown.
To turn on read-only mode, to the and disable the FlexReview for all of them.
When FlexReview is enabled for a team, the code reviews that are owned by a specific team based on CODEOWNERS will receive suggestions and review assignments. If there is a code change that encompasses more than one team, the reviews will be assigned only for the teams that have FlexReview enabled.
Along with team based enable / disable setting, FlexReview also has a global repository level setting. This global setting enables Aviator to index your past pull request data and GitHub teams data. When onboarding, you will enable global FlexReview to start indexing the data but it will still be in read-only mode. This state allows teams to test out the suggestions and status checks.
If you disable FlexReview, it will stop indexing the GitHub pull request data in the background. When it is disabled, the Slash commands for FlexReview will also stop working.