Issue
Contribution records
Contributors

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

Give credit to everyone
awm organization(s): Johnson & Johnson
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
alexpott organization(s): Acro Commerce, Thunder
dionsj volunteering
anushrikumari organization(s): OpenSense Labs
chike
ranjith_kumar_k_u organization(s): Zyxware Technologies
yashingole organization(s): QED42 customer(s): Drupal India Association
quietone organization(s): PreviousNext
rassoni organization(s): Material customer(s): Drupal India Association
aziza_a organization(s): Material
smustgrave organization(s): Mobomo
danielveza volunteering organization(s): PreviousNext
jordik
acbramley organization(s): PreviousNext
abhijith s volunteering organization(s): Zyxware Technologies
rakhi soni organization(s): Smashing Infolabs Pvt. Ltd. customer(s): Smashing Infolabs Pvt. Ltd.
rinku jacob 13 organization(s): Material customer(s): Drupal India Association
sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
gábor hojtsy 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.