Contribution records
Contributors

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

Give credit to everyone
rfay rfay
joachim joachim
nod_ nod_ volunteering
andypost andypost
sun sun
ianthomas_uk ianmthomasuk
xjm xjm organization(s): Acquia
jiv_e jiv_e volunteering
catch catch
fabianx Fabianx volunteering
yched yched
nlisgo nlisgo
dawehner dereine volunteering organization(s): Tag1 Consulting, Inc. customer(s): Drupal Association
twod twod volunteering
larowlan larowlan volunteering
effulgentsia effulgentsia organization(s): Acquia
joelpittet joelpittet volunteering
droplet droplet
olli olli
pwolanin pwolanin volunteering organization(s): Acquia
andyceo andyceo
steven jones darthsteven
wim leers wimleers organization(s): Acquia
Aki Tendo Aki_Tendo
tim.plunkett tim.plunkett organization(s): Acquia
damien tournoud damz
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.