Drupal and Git workflow using Acquia cloud

Question

Currently i have my central repo (origin repo) on a Bonobo Git Server.

I have followed those steps to use Acquia Cloud with a remote repository.

On my Acquia cloud repo i installed Drupal 8.

• also i already cloned my origin repo (Bonobo Git Server) locally to my computer.

Now i think the best workflow is to clone the Acquia Cloud repo locally isn’t it? With the whole Drupal 8 core and all files from the Drupal 8 installation.

So after that i can add contributed modules and themes to my local repo and commit and push them to my origin repo (Bonobo Git Server) and the Acquia Cloud repo?

1. Is this the a correct workflow? And how do i get all the Drupal 8
   files from Acquia Cloud to my local repo?
2. i have read also something about 'Translating your root directory with git subtree' in this article. Is this correct and what do i have to do exactly regarding my workflow
3. Is it advisable to use Acquia dev desktop also?

Answer 1

Disclaimer: I work for Acquia

This library article you linked to originates from an blog post that was written 4 years ago to answer questions about deploying from Jenkins build servers, private Github repos, etc. There's nothing specific to Acquia Cloud per se and it's rather a Git strategy you need to come up with for your development needs.

Is the Bonobo Git Server going to be the 'origin' going forward?

• If yes, then simply add the Acquia Cloud as a new remote (e.g. 'ac'). Git allows you to push to different remotes without any issue.
• If not, then you should make Acquia Cloud the 'origin' and Bonobo a regular remote (probably easier).

Since Git is decentralized, you 'own' the repo at any point in time and the main reason for keeping a remote is if you have a continuous integration system you need to pass your codebase through before you deploy code to Acquia Cloud. Another good reason is if you have a preferred Git workflow (think Github pull requests for instance) you wish to continue working with. But if you simply want to mirror your Acquia Cloud repo to (for instance) back it up, then I'd argue to just keep the Acquia Cloud repo and simplify your workflow.

The idea to keep in mind is you need only one checkout of your codebase. Having several remotes allows you to handle where to push to as described in the article.