Contribution records
Contributors

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

Give credit to everyone
hestenet hestenet organization(s): Drupal Association
anoopjohn anoopjohn organization(s): Zyxware Technologies
jijojoseph_zyxware jijojoseph_zyxware volunteering organization(s): Zyxware Technologies
mitthukumawat mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
fjgarlin fjgarlin volunteering organization(s): Drupal Association
poker10 poker10 organization(s): ActivIT s.r.o.
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
benjifisher benjifisher volunteering organization(s): Tag1 Consulting, Inc.
mcdruid mcdruid volunteering organization(s): Acquia
prasanth_kp prasanth_kp volunteering organization(s): Zyxware Technologies
fabianx Fabianx organization(s): HeroDevs
gábor hojtsy goba organization(s): Acquia
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.