Skip to content
Built for the new digital government
PHP CSS Gherkin JavaScript Makefile Ruby Other
Branch: 7.x-3.x
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Update config.yml Jan 23, 2019
.docker hotfix selenium/standalone-chrome:3.141.59-oxygen (#885) Jul 29, 2019
build/phing Update branch in and build/phing/build.xml Jan 23, 2019
css moved files back Apr 7, 2015
images moved files back Apr 7, 2015
js moved files back Apr 7, 2015
modules Merge branch '7.x-3.x' into feature/govcmsd7-64 Mar 1, 2019
tests Merge pull request #799 from suhyeonh1/GOVCMSD7-100 May 30, 2019
themes Fixed code linting issues with govcms_barton. Dec 10, 2018
.ahoy.yml Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
.dockerignore Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
.editorconfig Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
.env.default Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
.gitattributes Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
.gitignore Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
CHANGELOG.txt Prepended Changelog for 1.2.0-alpha5-7 Apr 16, 2015 Update branch in and build/phing/build.xml Jan 23, 2019
LICENSE.txt #289 - Add LICENSE.txt Jul 6, 2016 edit Mar 28, 2019 Added Lagoon, Ahoy and Docker support. (#715) Sep 18, 2018
build-govcms.make Switch back to development Aug 30, 2019
docker-compose.yml Fix Behat tests in the 7.x 3.x project (#750) Nov 9, 2018
drupal-org-core.make Update drupal/core to 7.67 (from 7.66) May 9, 2019
drupal-org.make Merge branch 'GOVCMSD7-115' of in… Aug 27, 2019 Fixed code linting issues with govcms profile. Dec 11, 2018
govcms.install Fix to replace creator value for the matatag dcterms.creator Mar 15, 2019
govcms.profile Fixed code linting issues with govcms profile. Dec 11, 2018
phpcs.xml Updated CodeSniffer ruleset and removed namespace of FeatureContext. Dec 11, 2018


Note: This release is not Acquia specific. Please continue to use 2.x release if you are in Acquia.


Packaged installation

govCMS exists as packaged versions on both the Github and project pages. These compressed archives are available in both zip and tar.gz format to download and use as needed.

Local development environment setup

  1. Make sure that you have Docker, Pygmy and Ahoyinstalled.
  2. Checkout project repository git clone
  3. ahoy up
  4. ahoy make
  5. ahoy install

This will construct a copy of the govCMS Drupal codebase in the docroot directory using instructions from the govcms.make file.

Once built, the profile files will be symlinked into /app/profiles/govcms.

List of available Ahoy workflow commands:

   build        Build project.
   cli          Start a shell inside CLI container.
   drush        Run drush commands in the CLI service container.
   install      Install the profile.
   lint         Lint code
   login        Login to a website.
   logs         Show Docker logs.
   make         Install local dependencies.
   ps           List running Docker containers.
   pull         Pull latest docker images.
   push         Push all docker images.
   release      Push all docker images.
   restart      Restart Docker containers.
   run          Run command inside CLI container.
   stop         Stop Docker containers.
   test         Run all tests.
   test-behat   Run behat tests.
   test-phpunit Run phpunit tests.
   up           Build project.



  • docroot - The Drupal root. This can be either a directory or a symlink.
  • - Project documentation written in markdown.
  • composer.json - Project specific vendor packages and repositories.
  • composer.lock - Locked in version of vendor packages. To ensure consistency across the project.
  • .gitignore - A list of files to be ignored by git. This is typically used for excluding local development modules and may create files to ignore that an IDE creates.


  • behat.yml - Provides all project specific behat configuration. Including regions and context configuration.
  • tests/behat - The directory where behat *.feature files are stored.

The ability to test a govCMS build is built into the repository with all tests run by Circle CI able to be run locally. Any changes made should be added and committed to your local repository and the following commands run:

ahoy test-behat
ahoy test-phpunit

Individual tests may be run by specifying the target for commands:

ahoy test-behat -- tests/behat/features/home.feature

Debugging CLI

To debug CLI commands, such as Behat tests, using XDEBUG:

  1. ahoy cli to get into test container.
  2. cd tests/behat
  3. . ../../vendor/bin/behat path/to/test.feature

Patching govCMS

Because govCMS is a Drupal distribution, modules and configurations are not added directly to the codebase. Rather, they are referenced within the govcms.make file.

Any alterations to Drupal core or contributed modules must have an associated issue filed against the project in question. Modifications should be made directly to the project in question and patched into govCMS rather than made directly against govCMS.

It is a requirement for any patches to govCMS to pass all automated testing prior to manual review. The automated testing checks for PHP syntax, coding standards, build completion and runs behavioural tests. It is also desirable that additions to the codebase add behat tests to ensure no regressions occur once committed.

To submit a patch, the govCMS project should be forked and changes applied to a branch on the forked repository. Once all changes are applied, a pull request between govCMS/master and the branch of the fork may be created.

Releasing govCMS


Contributing to govCMS

All contributions to govCMS are welcome. Issues and pull requests may be submitted against the govCMS project on github where they will be addressed by the govCMS team.

More information may be found in

You can’t perform that action at this time.