Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
b_sharpe organization(s): ImageX
johnwebdev
avpaderno
grayle organization(s): Dropsolid
Webbeh organization(s): Georgia Institute of Technology
larowlan organization(s): PreviousNext
smustgrave organization(s): Mobomo
nsciacca
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Google
weseze volunteering
acbramley organization(s): PreviousNext customer(s): Service NSW
alvarodemendoza volunteering
soutams
sandro_pagliara
remoschneider volunteering
randalv volunteering
bhogue organization(s): Pare & Co
samberry volunteering organization(s): NDP
christian.wiedemann
tim.plunkett organization(s): Acquia
luke.leber
geek-merlin organization(s): Geeks4Change, MachbarMacher
amitchell-p2 organization(s): Phase2
ressinel
vasike organization(s): DEHN digital solutions GmbH
godotislate volunteering
dk-massive
danielveza organization(s): PreviousNext
berdir organization(s): MD Systems GmbH
bkosborne
taran2l organization(s): Lemberg Solutions, Drupal Ukraine Community
rxjsx
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.