Contribution records
Contributors

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

Give credit to everyone
ccjjmartin ccjjmartin volunteering organization(s): Four Kitchens
darvanen Darvanen
kevinquillen kevinquillen organization(s): Velir
markdorison markdorison organization(s): Chromatic
megachriz megachriz volunteering
smustgrave smustgrave organization(s): Mobomo
damienmckenna damienmckenna organization(s): Current
heddn lucashedding organization(s): MTech, LLC
vinmayiswamy VinmayiSwamy volunteering organization(s): Material customer(s): Drupal India Association
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
mile23 Mile23 volunteering organization(s): CivicActions
shelane shelane
dww dww volunteering
agarzola agarzola organization(s): Chromatic
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
mandclu mandclu volunteering organization(s): Acquia
mark_fullmer markfullmer volunteering organization(s): University of Texas at Austin
nickdickinsonwilde NickDickinsonWilde volunteering organization(s): Taoti Creative
kristen pol kepol organization(s): Salsa Digital
luke.leber lleber
fathima.asmat fathima.asmat organization(s): CTI Digital
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.