A single pull request can be reviewed and merged, or multiple can be filed.Ī third, and truly insidious cost is where separate repositories actually become co-dependent, and no one knows it. With a single repository, you have a choice. Even if there’s only a master branch, there would still be three pull requests for this work-and they all have to be merged in the right order. For example, in site implementations, it’s really common to do some work in a custom module and then to theme that work in a custom theme. It’s easy to forget about that second pull request, and in our case, it led to constant questioning by the QA team to see if a given ticket was ready to test or not.Ī second cost is dealing with cross-repository dependencies. The first cost is that at best, every bit of work requires two pull requests one pull request in a custom module repository, and a second commit in the composer.lock in the site repository. It has the advantage of feeling familiar to the contrib workflow for Drupal modules, but there are significant costs to this model that only become obvious as code complexity grows. With the advent of Composer for Drupal site building, it feels natural to have many small, individual repositories for each custom module and theme. Try to use fewer repositories and projects After a recent launch, I went back and pulled together the common recommendations we made. Each of these clients had a large development team with significant amounts of custom code. Over the past two years, I’ve had the opportunity to work with many different clients on their Drupal 8 site builds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |