Contributing to BLT

BLT work is currently being tracked in the BLT GitHub issue queue and organized via a Kanban Board.

Please note the branch statuses documented in the README and GitHub page: - Pull requests for enhancements will only be accepted for the active development branch. - Pull requests for bug fixes will only be accepted for supported branches.

Developing BLT locally

If you'd like to contribute by actively developing BLT, we suggest that you clone BLT and also created a BLT-ed project for testing your changes.

Use the following commands to create a testable BLT-created project alongside BLT

git clone
rm -rf blted8
composer install --working-dir=blt
cd blt
./vendor/bin/robo create:from-symlink

Important While you do not have to have Ansible installed on your host machine in order to use blt, in order to boot the vm within the blted8 project which the above command creates, you will need Ansible installed on your host.

The new blted8 directory will have a composer dependency on your local clone of BLT via a ../blt symlink. You can therefore make changes to files in blt and see them immediately reflected in blted8/vendor/acquia/blt.


To execute the same "release" testing that is performed during CI execution, run:

./vendor/bin/robo release:test


See the PHPUnit section in the automated testing docs

Submitting Pull Requests

Changes should be submitted as Github Pull Requests to the project repository. To help with review, pull requests are expected to adhere to two main guidelines:

  1. PRs should be atomic and targeted at a single issue rather than broad-scope.
  2. PRs are expected to follow the template defined by the project in .github/