Issue
Contribution records
Contributors

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

Give credit to everyone
mlecha
hummeldon volunteering
mkimmet
generalredneck organization(s): Four Kitchens
dianacastillo organization(s): ITCON Services Inc.
javitan organization(s): CACI Digital Experience (formerly Cyber-Duck)
joegraduate organization(s): The University of Arizona
thomaswalther
vija
bonrita organization(s): iO
lmoeni organization(s): IT.NRW
Bzr
jsimonis
masipila volunteering
penyaskito organization(s): Lullabot
alphex
webdrips
ccarnnia volunteering
goz organization(s): Iosan
brianbrarian
dylan donkersgoed organization(s): Northern Commerce
vadym.tseiko volunteering organization(s): Drupal Ukraine Community, Lemberg Solutions
kurt.j
jcrump@tulane.edu
rajab natshah volunteering organization(s): Vardot customer(s): Vardot
shani maurya volunteering organization(s): Axelerant customer(s): Drupal India Association
jnicola
stewest volunteering organization(s): Sparks Interactive customer(s): Sparks Interactive
fengtan
handkerchief
Git commit message
Commit types
  • 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

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.