Contribution records
Contributors

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

Give credit to everyone
xtfer xtfer
jannakha jannakha volunteering organization(s): Tomato Elephant Studio
jaypan JayMatwichuk
campbellt_ campbellt_ organization(s): Lil Engine
marji marji
navkaur naav
owenlansbury owenlansbury
p_stampy pstampy
rosiehobbsy rosiehobbsy
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
drumm drumm organization(s): Drupal Association
xjm xjm organization(s): Acquia
skwashd skwashd organization(s): Dave Hall Consulting customer(s): Pfizer, Inc.
enzo-1 enzo-1
ivan zugec ivan.zugec organization(s): WebWash
daniel.nitsche daniel.nitsche
-enzo- enzo organization(s): weKnow Inc
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.