Contribution records
Draft
Contributors

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

Give credit to everyone
quicksketch quicksketch organization(s): Backdrop CMS
plach plach customer(s): Drupal Association
googletorp googletorp organization(s): Reveal IT
catch catch organization(s): Third and Grove
mirom mirom organization(s): i-KOS
strykaizer StryKaizer volunteering
webchick webchick organization(s): Acquia
swentel swentel
lokapujya lokapujya
berdir berdir organization(s): MD Systems GmbH
pwolanin pwolanin volunteering organization(s): SciShield
bloomt bloomt
5hawn 5hawn volunteering
gagarine gagarine volunteering
bkosborne bkosborne organization(s): Princeton University
xjm xjm volunteering organization(s): Acquia, xjm
ironnuts andrewfarq volunteering organization(s): Cactus Blossom IT Services Limited
gábor hojtsy goba organization(s): Acquia
stefan.r stefan.r
james.williams jameswilliams organization(s): ComputerMinds
alexpott alexpott organization(s): Acro Commerce, Thunder
amateescu amateescu customer(s): Tag1 Consulting, Inc.
effulgentsia effulgentsia organization(s): Acquia
meeni_dhobale meeni_dhobale volunteering organization(s): QED42
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.