Clone submodules during deployment allows you to use submodules in your Git repository. They are usually listed in a .gitmodules file at the root of your Git repository. When you push via Git, will try to clone them automatically.

Here is an example of a .gitmodules file:

[submodule "app/Oro"]
	path = src/Oro
	url =
[submodule "src/OroPackages/src/Oro/Bundle/EntitySerializedFieldsBundle"]
	path = src/OroPackages/src/Oro/Bundle/EntitySerializedFieldsBundle
	url =
[submodule "src/OroB2B"]
	path = src/OroB2B
	url =

When you run git push, you can see the output of the log:

Validating submodules.
  Updated submodule git:// 4 references updated.
  Updated submodule git:// 229 references updated.
  Updated submodule git:// 11 references updated.

Error when validating submodules 

If you see the following error:

Validating submodules.
  Found unresolvable links, updating submodules.

E: Error validating submodules in tree:
    - /src/Oro: Exception: commit 03567c6 not found.

   This might be due to the following errors fetching submodules:
    - HangupException: The remote server unexpectedly closed the connection.

Since the Git server cannot connect to GitHub via SSH without being granted an SSH key to do so, you should not use an SSH URL:, but you should use an HTTPS URL instead:

Use of private git repositories 

When using Git submodules that are hosted on private repositories, using the https protocol will fail with errors like:

GitProtocolError: unexpected http resp 401 for

To fix this, you need to:

  1. Change your .gitmodules file from HTTPS syntax to SSH syntax, e.g.


    [submodule "support/mymodule"]
        path = support/mymodule
        url =


    [submodule "support/mymodule"]
        path = support/mymodule
  2. Add the public key for the project from the project settings Deploy Key tab in the management console (see more about private repositories), which will allow our Git service to pull the module from the remote git service. This assumes you have configured the remote git repository to allow this by generating a private/public key pair. For example, see the Bitbucket documentation.

Removing submodules 

These steps are not specific to, but kept as a reference for Git so that submodules are effectively removed prior to entering the build process.

  1. Delete information for the submodule you’d like to remove from .gitmodules.

  2. Stage changes to .gitmodules:

    $ git add .gitmodules
  3. Remove the submodule’s configuration from .git/config.

  4. Remove the submodule from the repository (without trailing slash):

    $ git rm --cached path_to_submodule
  5. Remove the submodule’s files in .git from the repository (without trailing slash):

    $ rm -rf .git/modules/path_to_submodule
  6. Commit the changes:

    $ git commit -m "Removed submodule."
  7. Remove the submodule code locally, now untracked:

    $ rm -rf path_to_submodule