Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
sun
markhalliwell organization(s): Tag1 Consulting, Inc.
mgifford
fietserwin
webchick
draganeror
lewisnyman
yoroy
catch volunteering organization(s): Tag1 Consulting, Inc., Third and Grove
joelpittet organization(s): The University of British Columbia
Orizontal
bohemier volunteering
jofitz organization(s): ComputerMinds
tonifisler organization(s): Antistatique
rominronin
al0a organization(s): Dropsolid
mradcliffe organization(s): Kosada
jenlampton organization(s): Jeneration Web Development
larowlan organization(s): PreviousNext
alexpott volunteering
xjm organization(s): Acquia
effulgentsia organization(s): Acquia
andeersg organization(s): Bouvet
nikhil_110 organization(s): Material
rassoni organization(s): Material customer(s): Drupal India Association
smustgrave organization(s): Mobomo
mike stewart
star-szr organization(s): Northern Commerce
abhijith s volunteering organization(s): Zyxware Technologies
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.