Contribution records
Contributors

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

Give credit to everyone
jthorson jthorson customer(s): Drupal Association
robloach robloach
Crell Crell
msonnabaum msonnabaum
catch catch
xjm xjm
tstoeckler tstoeckler
renat renat
alexpott alexpott
klonos klonos
amateescu amateescu
berdir berdir
webchick webchick organization(s): Acquia
rfay rfay
ParisLiakos rootatwc
yesct YesCT
greggles greggles
chx chx
mile23 Mile23
nlisgo nlisgo
isntall isntall organization(s): Drupal Association
Mixologic Mixologic organization(s): Drupal Association
dawehner dereine volunteering
andypost andypost organization(s): Skilld
heddn lucashedding organization(s): Forum One, MTech, LLC
salvis salvis
drumm drumm organization(s): Drupal Association
David_Rothstein drothstein volunteering
jibran jibran volunteering
wim leers wimleers organization(s): Acquia
hass hass
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.