Contribution records
Contributors

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

Give credit to everyone
vuil i.vuchkov organization(s): Bulpros Consulting, JAKALA (formerly FFW)
berdir berdir
mile23 Mile23 volunteering
Mixologic Mixologic organization(s): Drupal Association
catch catch organization(s): Third and Grove
e0ipso e0ipso volunteering organization(s): Lullabot
lauriii lauriii organization(s): Acquia
mglaman mglaman organization(s): Centarro
mikelutz mdlutz volunteering organization(s): Four Kitchens, ICON Interactive
mradcliffe mradcliffe organization(s): Kosada
rpsu rpsu volunteering organization(s): Exove
svettes svettes organization(s): Acquia
tedbow tedbow organization(s): Acquia
xjm xjm organization(s): Acquia
lendude Lendude organization(s): iO
gábor hojtsy goba organization(s): Acquia
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
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.