Issue
Contribution records
Contributors

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

Give credit to everyone
immaculatexavier volunteering organization(s): Material customer(s): Drupal India Association
damienmckenna organization(s): Current
johnwebdev
berdir organization(s): MD Systems GmbH
ameymudras organization(s): Salsa Digital
nx2611 organization(s): Pantheon
hfernandes organization(s): ImageX
idebr organization(s): iO
richardrobinson volunteering
anon
gambry organization(s): EPAM
acbramley organization(s): PreviousNext customer(s): Service NSW
roaldnel organization(s): Finalist
anybody organization(s): DROWL.de
loopy1492
fenstrat organization(s): PreviousNext customer(s): Service NSW
mark_fullmer volunteering organization(s): University of Texas at Austin
thomwilhelm
wim leers organization(s): Acquia
alex.skrypnyk organization(s): DrevOps
kristen pol organization(s): Salsa Digital
rajab natshah organization(s): Vardot customer(s): Vardot
Git commit message
Commit types
  • 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

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.