Issue
Contribution records
Contributors

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

Give credit to everyone
nod_ organization(s): Très Bien Tech customer(s): Liip, OpenSense Labs, OPTASY, Palantir.net, Vardot
ahsannazir organization(s): QED42
shubh_ organization(s): QED42
smustgrave organization(s): Mobomo
utkarsh_33 volunteering organization(s): Acquia
quietone organization(s): PreviousNext
bnjmnm organization(s): Acquia
gauravvvv organization(s): Axelerant customer(s): Drupal India Association
rahulrasgon organization(s): QED42 customer(s): Drupal India Association
hooroomoo organization(s): Acquia
longwave organization(s): Full Fat Things
mstrelan
markconroy organization(s): Code Enigma
tom konda customer(s): Digital Circus
andy-blum organization(s): Lullabot
Sam Phillemon volunteering organization(s): QED42
Theresa.Grannum organization(s): Acquia
omkar-pd 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.