Contribution records
Contributors

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

Give credit to everyone
volkswagenchick volkswagenchick organization(s): The Linux Foundation
bernardm28 bernardm28 volunteering organization(s): Vaultes
crawleyhost crawleyhost volunteering organization(s): Bright Plum, Inc. customer(s): Drupal Association
ctrladel ctrlADel volunteering organization(s): Perficient
daggerhart daggerhart organization(s): Daggerhart Lab
dineshkumarbollu dineshkumarbollu organization(s): Valuebound customer(s): Valuebound
dorficus dorficus organization(s): EPAM
elenat elenat
imrodmartin imrodmartin
kswamy KalaiselvanSwamy volunteering organization(s): Axelerant customer(s): Drupal India Association
markie markie organization(s): Kanopi Studios
neerajskydiver neerajskydiver volunteering organization(s): Valuebound
nilubol nilubol volunteering
richgerdes richgerdes organization(s): Unleashed Technologies customer(s): Dixon Valve
sevines sevines
stephenpashby stephenpashby
lisa.rae lhridley volunteering
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.