Issue
Contribution records
Contributors

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

Give credit to everyone
betalister organization(s): Drupal Association
aburke626 organization(s): amazee.io
aimeerae organization(s): Hook 42
bendygirl
bradleyfields
cgreaten organization(s): Bounteous
chadhester volunteering
davidhernandez organization(s): JAKALA (formerly FFW)
dinarcon organization(s): Agaric
dmkelner
edddj volunteering
estamatic
ethomas08 volunteering
jasonawant organization(s): Nerdery customer(s): Nestle Purina PetCare - United States
jerdavis organization(s): Horizontal
katherined
mariohernandez volunteering organization(s): Current
mdstamm volunteering
rainbreaw volunteering
rubyji organization(s): MomsRising
sarawberg
Webbeh organization(s): Georgia Institute of Technology
starshaped organization(s): Lullabot
stpaultim organization(s): Triplo
sushyl organization(s): Axelerant
ultrabob
allie micka organization(s): bluebird.io customer(s): bluebird.io
dwells-tn volunteering
erin.rasmussen
rahul.shinde organization(s): Axelerant, DevsAdda customer(s): HighWire Press, Inc
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.