Contribution records
Draft
Contributors

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

Give credit to everyone
effulgentsia effulgentsia organization(s): Acquia
nod_ nod_ organization(s): Smile
seanb seanB
alexpott alexpott organization(s): Acro Commerce, Thunder
anmolgoyal74 anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
alfaguru alfaguru organization(s): Figure W Limited
blainelang blainelang
anchal_gupta Anchal_gupta12 organization(s): Material customer(s): Drupal India Association
rauch rauch
berliner berliner
smustgrave smustgrave organization(s): Mobomo
chaseontheweb ChaseOnTheWeb
lauriii lauriii organization(s): Acquia
anybody Anybody volunteering organization(s): DROWL.de
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
Ice-D Ice-D
krzysztof domański krzysztof_domanski organization(s): abventor
manuel garcia manuelgarcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
chris burge ChrisBurge organization(s): University of Nebraska
webflo webflo organization(s): UEBERBIT GmbH
oily andrewfarq volunteering organization(s): Cactus Blossom IT Services Limited
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.