Contribution records
Draft
Contributors

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

Give credit to everyone
dpolant dpolant
miro_dietiker mirodietiker organization(s): MD Systems GmbH
jamiehollern jamiehollern volunteering
fearlsgroove fearlsgroove organization(s): Alloy Magnetic
omarlopesino omarlopesino volunteering organization(s): Metadrop
anybody Anybody organization(s): DROWL.de
brooke_heaton brooke_heaton
mrchristophy mrchristophy
colan colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
berdir berdir organization(s): MD Systems GmbH
andypost andypost volunteering organization(s): Skilld
vacho vacho organization(s): Skilld
ezeedub ezeedub organization(s): Phase2
oleksiy Shdulin organization(s): Skilld customer(s): Drupal Ukraine Community
sorlov sorlov organization(s): Skilld
twod twod organization(s): Websystem
dubs dubs
urvashi_vora urvashivora organization(s): Valuebound customer(s): Valuebound
capysara capysara organization(s): Bounteous
it-cru it-cru
jeroen.b jeroen.b organization(s): .VDMi/
gaëlg gaelg organization(s): Insite
mattlc mattlc organization(s): Iosan
davidpetit DavidPetit
benstallings BenStallings organization(s): Encore Healthcare
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.