Issue
Contribution records
Contributors

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

Give credit to everyone
tuhongwei volunteering
labboy0276
arnoldbird
apermuy
pnagornyak
estoyausente volunteering
hungry_mind
slydevil
sivaprasadc volunteering organization(s): DrupalPartners customer(s): Binary Works
jedsaet volunteering
wundo organization(s): Chuva Inc. customer(s): Galoa Science
kpoornima volunteering organization(s): Melity
tiikeri
lolandese organization(s): Cognizant Technology Solutions
justkristin
pene organization(s): Cheppers
xjm volunteering
xem8vfdh
@baux
Mahima Prachandia
chris matthews volunteering organization(s): City of Oaks Design
lisa.rae volunteering organization(s): FRUITION
qusai taha organization(s): Vardot
proweb.ua
bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
malcomio organization(s): Capgemini
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.