Issue
Contribution records
Contributors

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

Give credit to everyone
mglaman volunteering organization(s): Acquia
jeroent organization(s): iO
mherchel
rlahoda volunteering
btully
Webbeh organization(s): Georgia Institute of Technology
jwilson3 organization(s): Bluespark
adamps organization(s): AlbanyWeb
purencool organization(s): Acquia
neclimdul organization(s): APQC
rabbitlair organization(s): Lullabot customer(s): IndieCommerce - Website Development for Independent Booksellers
bronzehedwick organization(s): Lullabot
lauriii organization(s): Acquia
dan_metille
ressa organization(s): Ardea
callinmullaney organization(s): Four Kitchens
hbrokmeier
mndonx organization(s): Four Kitchens
benjifisher volunteering organization(s): Tag1 Consulting, Inc.
akalata organization(s): Tag1 Consulting, Inc.
ckrina organization(s): Lullabot
dww volunteering
alexpott organization(s): Acro Commerce, Thunder
bnjmnm organization(s): Acquia
smustgrave organization(s): Mobomo
crasx volunteering organization(s): Bounteous
generalredneck organization(s): Four Kitchens
lugir volunteering
chi
tim.plunkett organization(s): Acquia
andy-blum organization(s): Lullabot
neslee canil pinto organization(s): Ramsalt Lab customer(s): Drupal India Association
ghost of drupal past organization(s): Smartsheet
star-szr
wim leers organization(s): Acquia
jen.stein
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.