Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
gbrewer
jproctor
ahebrank
merauluka organization(s): Current, Red Hat
bkosborne organization(s): Princeton University
robertragas organization(s): Open Social
bobbysaul
b0gucki3 volunteering
sutharsan organization(s): ronder
dgaspara organization(s): NTT DATA
hchonov organization(s): 1xINTERNET
guypaddock organization(s): Inveniem
smustgrave organization(s): Mobomo
trickfun
cmd87 organization(s): 1xINTERNET
bluegeek9 volunteering
liquidcms
sharonho organization(s): Reading Room
nieuwkar
rainer f. gottlieb
b.lammers organization(s): Youwe
neslee canil pinto organization(s): Ramsalt Lab, Specbee customer(s): Drupal India Association
arthur.baghdasar organization(s): Vectus
remco hoeneveld volunteering organization(s): iO customer(s): Erasmus University Rotterdam
nsalves organization(s): NTT DATA
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.