Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
fago organization(s): drunomics
catch organization(s): Third and Grove
ericdsd
heni_deepak
jungle volunteering
alexpott organization(s): Acro Commerce, Thunder
smustgrave organization(s): Mobomo
extexan
heddn organization(s): MTech, LLC
joegraduate organization(s): The University of Arizona
suryabhi
mrinalini9 organization(s): Material customer(s): Drupal India Association
BBaptiste
bjc2265
rajeshreeputra volunteering organization(s): Shivswarajya Inc.
prabuela volunteering organization(s): Specbee customer(s): Specbee
eiriksm organization(s): Foreningen Drupal Norge, Frontkom, Violinist
hfernandes organization(s): ImageX
jeroent organization(s): iO
ciprian.stavovei organization(s): drunomics
ravi.shankar organization(s): OpenSense Labs
joseph.olstad
lucian.ilea
Ajeet Tiwari organization(s): OpenSense Labs customer(s): DrupalFit
eric_a
rajab natshah organization(s): Vardot customer(s): Vardot
jlockhart
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.