Contribution records
Contributors

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

Give credit to everyone
mondrake mondrake volunteering
andypost andypost volunteering organization(s): Skilld
benmorss benmorss
avpaderno avpaderno volunteering
hestenet hestenet organization(s): Drupal Association
catch catch organization(s): Tag1 Consulting, Inc., Third and Grove
xjm xjm organization(s): xjm
Mixologic Mixologic organization(s): Drupal Association
quietone quietone organization(s): PreviousNext
mstrelan mstrelan organization(s): PreviousNext
nod_ nod_ volunteering organization(s): Eclipse Foundation
jwilson3 jwilson3 organization(s): Bluespark
smustgrave smustgrave organization(s): Mobomo
luksak luksak volunteering organization(s): ATTRIBUTE customer(s): ATTRIBUTE
larowlan larowlan organization(s): PreviousNext
heddn lucashedding organization(s): MTech, LLC, Tag1 Consulting, Inc.
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
alexpott alexpott organization(s): Acro Commerce, Thunder
longwave longwave organization(s): Full Fat Things
cilefen cilefen
wim leers wimleers organization(s): Acquia
pere orga netol volunteering
kim.pepper kimpepper organization(s): PreviousNext
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.