Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
lauriii organization(s): Acquia
mgifford organization(s): OpenConcept Consulting Inc.
andrewmacpherson volunteering organization(s): Annertech
shaal volunteering organization(s): Palantir.net
bnjmnm organization(s): Acquia
eleleka organization(s): Skilld
fhaeberle
huzooka organization(s): Cheppers customer(s): Acquia
mradcliffe organization(s): Kosada
kostyashupenko organization(s): Skilld
deepalij organization(s): QED42 customer(s): Drupal India Association
gauravvvv organization(s): OpenSense Labs
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
nod_ volunteering organization(s): Acquia
imalabya organization(s): Specbee customer(s): Drupal India Association
volkswagenchick organization(s): Kanopi Studios
smustgrave organization(s): Mobomo
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
ckrina organization(s): Lullabot
martijn.cuppens organization(s): iO
sakthivel m organization(s): QED42 customer(s): Drupal India Association
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.