-[Guidelines for implementing Enterprise Edition features](ee_features.md)
-[Guidelines for implementing Enterprise Edition features](ee_features.md)
-[Security process for developers](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md#security-releases-critical-non-critical-as-a-developer)
-[Security process for developers](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md#security-releases-critical-non-critical-as-a-developer)
-[Requesting access to Chatops on GitLab.com](chatops_on_gitlabcom.md#requesting-access)(for GitLabbers)
-[Requesting access to Chatops on GitLab.com](chatops_on_gitlabcom.md#requesting-access)(for GitLabbers)
@@ -168,7 +168,6 @@ This branch is the place for any work related to this change.
...
@@ -168,7 +168,6 @@ This branch is the place for any work related to this change.
NOTE: **Note:**
NOTE: **Note:**
The name of a branch might be dictated by organizational standards.
The name of a branch might be dictated by organizational standards.
For example, in GitLab, any branches in GitLab EE that are equivalent to branches in GitLab CE [must end in `-ee`](../development/automatic_ce_ee_merge.md#cherry-picking-from-ce-to-ee).
When you are done or want to discuss the code, open a merge request.
When you are done or want to discuss the code, open a merge request.
A merge request is an online place to discuss the change and review the code.
A merge request is an online place to discuss the change and review the code.