Preparing Elastic Path Commerce Source Code

Ensure that you have the following:

Access to a Git hosting service.
GitLab specific credentials on code.elasticpath.com. For more information on creating a GitLab account, see the Set up your GitLab specific credentials section in the documentation.
Access to the Elastic Path Maven repository.
Note: Your Elastic Path Support Portal Account page lists your Maven credentials. If you do not have these credentials, submit a ticket on the page.

This section provides instructions to prepare Elastic Path Commerce source code for your project.

Navigate to https://code.elasticpath.com/ep-commerce/ep-commerce.
Clone the Git repository.

Note: When you clone an Elastic Path Commerce repository for the first time, follow the instructions in the Cloning via HTTPS guide.

Warning: Windows File Path Limitation - Do not clone to a directory with a file path greater than 20 characters. Windows file paths are limited to 260 characters. The longest file path in the source code is greater than 230 characters.
Tip:
Configure Git to convert line ending to LF on input.
The command to configure this is:
```
git config --global core.autocrlf input
```
Check out the correct branch and release version of Elastic Path Commerce.

Tip: Each version branch contains the source code for the release and the subsequent patches. Enable Watch for the repository to get notification of any updates.
Create a development branch in your local repository. The branch name depends on the SCM and branch naming conventions.
Add the Elastic Path Commerce repository to your Git hosting service.
Push the development branch to the Git hosting service.

Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site