Contribution records
Draft
Contributors

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

Give credit to everyone
plach plach volunteering organization(s): Tag1 Consulting, Inc. customer(s): American Federation of Teachers, Drupal Association
mile23 Mile23
tstoeckler tstoeckler
avpaderno avpaderno volunteering
catch catch organization(s): Tag1 Consulting, Inc., Third and Grove
sam152 sam volunteering organization(s): PreviousNext
jibran jibran volunteering organization(s): PreviousNext
hchonov hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
amateescu amateescu customer(s): Pfizer, Inc.
dwkitchen dwkitchen organization(s): Johnson & Johnson
kristiaanvandeneynde kristiaanvandeneynde organization(s): Factorial.io
ccarrascal ccarrascal organization(s): Johnson & Johnson
joachim joachim
mglaman mglaman volunteering
ankithashetty AnkShetty volunteering organization(s): Specbee
bhanu951 Bhanu951 volunteering
smustgrave smustgrave organization(s): Mobomo
wim leers wimleers organization(s): Acquia
mangy.fox mangy.fox
guilmour-asc guilmour-asc organization(s): CI&T
fago fago
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.