Contribution records
Contributors

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

Give credit to everyone
jdleonard jdleonard volunteering organization(s): Modern Biz Consulting
thejimbirch thejimbirch organization(s): Kanopi Studios
aangel aangel organization(s): Performant Labs
alexpott alexpott organization(s): Acro Commerce, Thunder
Artem Artem
benjifisher benjifisher volunteering
b_sharpe b_sharpe organization(s): ImageX
dww dww volunteering
eclipsegc eclipsegc
guptahemant guptahemant volunteering organization(s): QED42 customer(s): Drupal India Association
markie markie organization(s): Lullabot
phenaproxima phenaproxima organization(s): Acquia
rachelh_design rachelh_design organization(s): Oomph, Inc.
realityloop realityloop volunteering organization(s): Realityloop
sonfd sonfd organization(s): DevCollaborative, LLC
ultrabob ultrabob organization(s): Kalamuna customer(s): Metropolitan Transportation Commission
hestenet hestenet organization(s): Drupal Association
kristen pol kepol organization(s): QuantCDN, Salsa Digital
rajab natshah RajabNatshah organization(s): Vardot customer(s): Vardot
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.