Contribution records
Contributors

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

Give credit to everyone
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
_pratik_ k_pratik volunteering organization(s): Specbee customer(s): Drupal India Association
annmarysruthy annmarysruthy organization(s): QED42 customer(s): Drupal India Association
nmorin nmorin volunteering
dhigby dhigby
avpaderno avpaderno volunteering
sourabhjain sourabh_jain_419 organization(s): Valuebound customer(s): Valuebound
shank115 Shank115 organization(s): Specbee customer(s): Drupal India Association
yashaswi18 Yashaswi18
pray_12 Preethy_ray organization(s): Specbee
chandansha Chandansha organization(s): cmsMinds
roberttabigue roberttabigue organization(s): Promet Source
anybody Anybody organization(s): DROWL.de
zkhan.aamir zkhan.aamir organization(s): Specbee customer(s): Drupal India Association
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.