## Problem to Solve This epic is to define requirements for how to import GitHub protected rules (rules for protected branches). The definition of GitHub protected branches is different from protected branches in GitLab. These requirements map GitHub protected rules to GitLab general settings/features. In some cases we don't have any similar feature in GitLab to some of the GitHub rules, so those rules will be loosed when migrating to GitLab. Once we will validate those requirements we will create a separate issue for each requirement **Feature**: Branch protection rules ```gherkin Scenario: "Allow force pushes" - "everyone" Given "Allow force pushes" is defined in GitHub repository as a branch protected rule, and "Everyone" is selected When a user imports this repository to GitLab Then "Allowed to force push" will be check on in GitLab settings, and "Allowed to push" will include Developers and Maintainers. Scenario: "Allow force pushes" - "Specify who can force push" Given "Allow force pushes" is defined in GitHub repository as a branch protected rule, and "Specify who can force push" is selected, and a list of people, teams or apps is listed. When a user imports this repository to GitLab Then "Allowed to force push" will be check on in GitLab settings, and "Allowed to push" will include the same users as defined in GitHub. But teams or apps will not be set in GitLab. Scenario: "Require conversation resolution before merging" Given "Require conversation resolution" before merging is defined as a branch protected rule in GitHub When a user imports this repository to GitLab Then the settings All threads must be resolved in the GitLab project settings will be enabled Scenario: "Require signed commits" Given "Require signed commits" a branch protected rule in GitHub checked When a user imports this repository to GitLab Then the settings "Reject unsigned commits" in the GitLab project settings will be enabled Scenario: "Require status checks to pass before merging" Given "Require status checks to pass before merging" protected rule is defined in GitHub When a user imports this repository to GitLab Then the service names in settings Status checks settings in Merge Request settings in the GitLab will be available Scenario: Require a pull request before merging When enabled, all commits must be made to a non-protected branch and submitted via a pull request before they can be merged into a branch that matches this rule. Given "Require a pull request before merging When enabled, all commits must be made to a non-protected branch and submitted via a pull request before they can be merged into a branch that matches this rule." protected rule is defined in GitHub When a user imports this repository to GitLab Then in GitLab protected branch settings, in the Allowed to merge list, Developers + Maintainers will be selected, and in the Allowed to push list, No one will be selected. Scenario: "Create an issue with import summary" Given I have a project in GitHub When I import this repository to GitLab Then a new issue will be created in GitLab, will be assigned to me, with Migration details, what imported succesfully, and what are the gaps that the user needs to manually configure. ``` **Feature**: Branch tags ```gherkin Scenario: Migrate branch tags Given my GitHub branches have tags When I import the repository to GitLab Then all tags will be migrated for each branch, and similar tags will be available in GitLab ```