Drupal and Git workflow using Acquia cloud
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.