There's a new tool that does most of what I need: integratedexperts/robo-git-artefact.
I don't want deployment related commits in Github, but I do want the Acquia repo to show the commit history from Github.I have Acquia's Dev environment pointing to the Acquia master branch.I want to push whatever branch I'm on into the Acquia master branch.I have downloaded my Acquia Drush aliases file.I'm using composer to manage my Drupal (7 or 8) codebase.Run some Drush commands to rebuild caches and run updates.Optionally remove any other non-production stuff we don't want.gitignore so we can commit all the things (vendor directory etc) The process I want is something like this: To me, the Acquia Git repo is just a part of the Acquia hosting mechanism.
#Acquia hosting full#
In this example, I'm not fussy about the Git repo on Acquia because I am keep the full history on Github. What we'll do is take a project that is built with composer, and provide a mechanism to push the code to our Git repository on Acquia.
Practices have changed a lot since then, we are much more likely to use Bitbucket or Github as the canonical Git repo, and we usually don't commit our dependencies such as the vendor directory - we have build tools to do this for us.Ī number of tools have evolved at Acquia, such as BLT and Pipelines, that give us a way to automate processes across their infrastructure, but they're not always the best choice for a project, usually because they add a lot of Acquia-specific complexity. With Drupal 7, we committed all our code and pushed it to Acquia. When Acquia first launched its hosting platform, most of the projects I was involved in used the Acquia git repository as the canonical origin.
0 kommentar(er)
