Contribution records
Contributors

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

Give credit to everyone
jumoke Jumoke
maxocub maxocub volunteering
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
wgallop99 wgallop99
ramonma1989 ramonma1989 organization(s): University of Informatics Sciences
vgardner vgardner
neelam_wadhwani neelam_wadhwani organization(s): Valuebound customer(s): Valuebound
prabha1997 prabha1997 organization(s): Valuebound customer(s): Valuebound
jungle jungle volunteering
quietone quietone volunteering
mikelutz mdlutz volunteering organization(s): Four Kitchens
alexrayu alexrayu volunteering
bachbach bachbach
thomaswalther thomaswalther
felubra felubra
grevil Grevil organization(s): DROWL.de
huzooka huzooka volunteering organization(s): Kibit Solutions customer(s): Kibit Solutions
anybody Anybody organization(s): DROWL.de
4kant 4kant
steve hanson SteveHanson organization(s): Cruiskeen Consulting LLC
dhirendra.mishra dhirendramishra10 organization(s): Valuebound customer(s): Valuebound
vlad.dancer vlad.dancer volunteering organization(s): Drupal Ukraine Community, Xspace
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.