Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): The Linux Foundation
mradcliffe mradcliffe organization(s): Kosada
lostcarpark lostcarpark volunteering
Amarshall Amarshall volunteering
bsnodgrass bsnodgrass organization(s): net2Community, Inc.
cellear cellear volunteering
chrisdarke ChrisDarke organization(s): MindAtomic
greggmarshall greggmarshall volunteering
hestenet hestenet organization(s): Drupal Association
joecrespo jcrespo
markie markie organization(s): Lullabot
shriaas Shriaas volunteering organization(s): QED42 customer(s): Drupal India Association
ultimike ultimike organization(s): DrupalEasy
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
xjm xjm organization(s): HeroDevs, xjm
john cook johncook organization(s): Cojolan customer(s): Annertech
kristen pol kepol organization(s): Salsa Digital
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.