Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
seanb
weseze volunteering
andrewmacpherson volunteering
phenaproxima organization(s): Acquia
johnwebdev
alexpott organization(s): Thunder
amateescu customer(s): Pfizer, Inc.
bnjmnm organization(s): Acquia
oknate volunteering
vsujeetkumar organization(s): Material customer(s): Drupal India Association
berdir organization(s): MD Systems GmbH
stomusic
dejan0 organization(s): acolono GmbH
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
ankithashetty volunteering organization(s): Specbee
johnpitcairn
marcoscano volunteering organization(s): Lullabot customer(s): New Relic
joachim organization(s): Factorial.io
anybody organization(s): DROWL.de
Belshi
a.milkovsky volunteering
wim leers organization(s): Acquia
chr.fritsch organization(s): Thunder
ghost of drupal past organization(s): Smartsheet
joseph.olstad
geek-merlin organization(s): Geeks4Change, MachbarMacher
martijn de wit organization(s): Ablerz
yautja_cetanu organization(s): FreelyGive
drdam
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.