Endevor Bridge for Git recommended strategy to protect branch

Products

• Endevor

Issue/Introduction

What is the recommended strategy or way to protect bridged sync branch, but still allow for bridge to sync from Endevor into the sync branch?

Environment

BR4G -All releases.

Using Github App

Cause

When a branch is not protected and code not reviewed; users can end up with bad codes during a pull request. 

Resolution

The main requirement for Endevor Bridge for Git is that the mapping owner is able to push to synchronized branches.

You can set up rules for other users and DO NOT enable the checkbox:

"DO NOT allows bypassing the above settings"
The above settings will apply to administrators and custom roles with the "bypass branch protections" permission.
 
That way you can have the mapping owners be administrators of the github repositories or have a custom role that allows them to bypass the branch protections rule.

You can also experiment with "Require conversation resolution before merging"