Git requirements

This page lists detailed requirements for using Git with Magento Enterprise Cloud Edition.

Source control with Git

Any change you make to your Magento Enterprise Cloud Edition project must be committed to a Git repository. You can use either the repository provided with your account or you can use your own private account on GitHub. For more information, see Magento Enterprise Cloud Edition repositories.

If you don’t already have an account, we’ll create one for you. However, if you have a GitHub account and you’re already using it in a development workflow, we recommend you use it.

To clone a Magento reference project, you must upload SSH keys to github.com.

Your project's master branch always uses the provided Git repository. You can use an existing GitHub account to manage branches of that repository. (Branches are also referred to as environments.

Git knowledge

We assume you have a good working knowledge of Git. If not, consult the following resources:

Before getting started, make sure you have a Git client installed on your computer to be able to interact with Magento Enterprise Cloud Edition.

In addition to Git's requirements for valid branch names, Magento Enterprise Cloud Edition adds two additional requirements:

  • The / character isn't allowed.
  • Branch names must be case-insensitively unique. In other words, if you have a branch named _CaSe_, you cannot create another branch named _case_.

You must use Secure Shell (SSH) and not HTTPS to connect to the Git repository. For more information, see GitHub documentation.