Contribution records
Contributors

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

Give credit to everyone
huzooka huzooka organization(s): Cheppers customer(s): Acquia
alison alison volunteering
heddn lucashedding organization(s): MTech, LLC
kapilv kapilkumar0324 volunteering organization(s): Innoraft customer(s): Drupal Association, Drupal Care
quietone quietone volunteering
grevil Grevil volunteering organization(s): DROWL.de
anybody Anybody volunteering
jeroent JeroenT organization(s): iO
ajaypratapsingh ajay-wq organization(s): Material customer(s): Drupal India Association
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
andypost andypost volunteering organization(s): Skilld
danflanagan8 danflanagan8 organization(s): Horizontal
wim leers wimleers organization(s): Acquia
hemant bansal hemant.bansal volunteering organization(s): Dotsquares Ltd.
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.