Source Code Access
Ensure that you have the following:
- Access to your own Git based SCM (Source Code Management) tool
- GitLab specific credentials on
- Access to the Elastic Path Maven repository
Your Elastic Path Support Portal Account page lists your Maven credentials. If you do not have these credentials, submit a ticket on the page.
Cloning Git Repository
https://code.elasticpath.com/ep-commerce/ep-commerceand clone the Git repository
git clone https://code.elasticpath.com/ep-commerce/ep-commerce
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
Configure Git to convert line ending to
LF on input. The command to configure this is:
git config --global core.autocrlf input
Checking out a Release Branch
- Check out the correct branch of release version of Elastic Path Commerce.
The branches are named as
majorindicates major release version
minorindicates minor release version
xindicates patch updates
git checkout -b release/<major>.<minor>.x
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.
Pushing to Your Repository
Create a development branch in your local repository from the released version branch that is checked out previously.
The branch name depends on the SCM and your branch naming conventions. For example:
git checkout -b <my-org-ep-release-dev>
Add the Elastic Path Commerce repository to your own Git hosting service.
git remote add <remote-name> <my-git-repo-url>
Push the development branch to your own Git hosting service.
git push <remote-name> <my-org-ep-release-dev>