Issue
Contribution records
Contributors

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

Give credit to everyone
sagesolutions
Maschenmode volunteering
strykaizer volunteering organization(s): ClicketyClick
Jl6owa
retrodans organization(s): Agile Collective
devad volunteering
karimb volunteering
marcoka
vradova
gsquirrel
WiseMike
ckng organization(s): O8
meenakshig organization(s): Material customer(s): Drupal India Association
fmb
fabianderijk organization(s): Finalist
volker23
minoroffense organization(s): Coldfront Labs Inc.
glugmeister
init90 organization(s): Drupal Ukraine Community, ZANZARRA Drupal Agency
scorpionghost
guy_schneerson
nno
hongqing
ifrik organization(s): ISSUP
fallenturtle
krug volunteering
qusai taha organization(s): Vardot
ahmad abbad volunteering organization(s): Vardot customer(s): Vardot
johan den hollander organization(s): Finalist
proweb.ua
denes.szabo volunteering
joseph.olstad
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.