Issue
Contribution records
Contributors

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

Give credit to everyone
johnpicozzi organization(s): EPAM
benjifisher volunteering organization(s): FRUITION
brianperry organization(s): Pantheon
codekarate organization(s): Gatsby
ctrladel organization(s): Perficient
dbungard organization(s): JAKALA (formerly FFW)
dmkelner
Dorf
hotwebmatter organization(s): Esteemed
imrodmartin
JRastaban organization(s): Pantheon
jrockowitz volunteering organization(s): The Big Blue House, Webform module Open Collective
kclarkson organization(s): Blend Me, Inc
leslieg organization(s): Redfin Solutions, LLC
mikemiles86 volunteering
nicxvan organization(s): nLightened Development LLC
vonreyes organization(s): Drupal Association
yurtboy
andy-blum organization(s): Lullabot
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.