All Collections
Git Integration
Branch Protection Rules
Branch Protection Rules

Using the right project type if you have branch protection

Alan Parkinson avatar
Written by Alan Parkinson
Updated over a week ago

If your organisation uses branch protections on its base/master branch then you most likely will be using a Feature-Branching strategy where features and changes are added to the base branch via a pull request. Feature-branching with Behave Pro, would be the best solution for you as Behave Pro will create new branches for each of your Jira issues and will only read from the base branch and never make commits to it.

If you use a trunk-based strategy you will need to ensure that the base branch does not have protections, unlike feature-branching Behave Pro will make commits directly to your base branch to add or make changes to the feature files that it produces.

You can additionally use a classic style project without the Git functionality if you would rather manually import the feature files to where you want them, so long as your branch protections allow for this.

Did this answer your question?