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
bentekwork organization(s): Pantheon
brenda003
chadhester volunteering
ckrina organization(s): Lullabot
dsquaredb organization(s): DSquaredB Consulting, LLC
davidhernandez organization(s): JAKALA (formerly FFW)
dboeger volunteering
gabesullice organization(s): Acquia
gargsuchi volunteering
greggmarshall volunteering
nickdickinsonwilde volunteering organization(s): Taoti Creative
jerdavis organization(s): Horizontal
katherined
logickal organization(s): Third and Grove
mariohernandez volunteering organization(s): Current
mdstamm volunteering
mikeohara volunteering
nonsie
Webbeh organization(s): Georgia Institute of Technology
yesct organization(s): Lullabot customer(s): IBM
rainbreaw volunteering
rubyji organization(s): MomsRising
sparklingrobots
starshaped organization(s): Lullabot
stpaultim organization(s): Triplo
switzern organization(s): Elevated Third
allie micka organization(s): bluebird.io customer(s): bluebird.io
erin.rasmussen
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.