Issue
Contribution records
Contributors

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

Give credit to everyone
huzooka organization(s): Cheppers customer(s): Acquia
ckrina organization(s): Lullabot
saschaeggi volunteering organization(s): Unic
bnjmnm organization(s): Acquia
kostyashupenko organization(s): Skilld
lauriii organization(s): Acquia
nod_ volunteering organization(s): Smile
katherined
andypost volunteering organization(s): Skilld
andrewmacpherson volunteering
klonos organization(s): Backdrop CMS
gauravvvv organization(s): Material, OpenSense Labs customer(s): Drupal India Association
chetanbharambe organization(s): QED42 customer(s): Drupal India Association
vikashsoni volunteering organization(s): Zyxware Technologies
mherchel
rootwork
mgifford
rkoller
shaal volunteering organization(s): Phase2
dww organization(s): TEN7
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
acbramley organization(s): PreviousNext customer(s): Service NSW
sakthivel m organization(s): QED42 customer(s): Drupal India Association
ravi.shankar organization(s): OpenSense Labs
rinku jacob 13 organization(s): Zyxware Technologies
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.