Contribution records
Contributors

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

Give credit to everyone
jfussion jfussion volunteering
fgm fgm organization(s): OSInet
akshay_d akshay_d organization(s): Specbee
xem8vfdh xeM8VfDh
berdir berdir organization(s): MD Systems GmbH
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
sja112 sja112 organization(s): Material customer(s): Drupal India Association
heddn lucashedding organization(s): MTech, LLC
jcnventura jcnventura organization(s): 1xINTERNET
jurriaanroelofs peach
klidifia klidifia
sahana _n Sahana16081996 organization(s): Specbee
kristen pol kepol organization(s): Hook 42
neslee canil pinto NesleeCanilPinto organization(s): Specbee
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.