Contribution records
Contributors

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

Give credit to everyone
gauravvvv Gauravmahlawat organization(s): Material, OpenSense Labs customer(s): Drupal India Association
chetanbharambe chetan18 organization(s): QED42 customer(s): Drupal India Association
guilhermevp guilhermevp organization(s): CI&T
catch catch organization(s): Third and Grove
sagarchauhan sagarchauhan organization(s): Material customer(s): Drupal India Association
bnjmnm bnjmnm organization(s): Acquia
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
mherchel mherchel
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
lauriii lauriii volunteering
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
sakthivel m SakthivelM organization(s): QED42 customer(s): Drupal India Association
Shubham Sharma 77 Shubham-Sharma-77 organization(s): Material customer(s): Drupal India Association
aamir m AamirM1_99 organization(s): QED42 customer(s): Drupal India Association
rakhi soni rakhi_soni organization(s): Smashing Infolabs Pvt. Ltd. customer(s): Smashing Infolabs Pvt. Ltd.
aarti zikre aartiz volunteering organization(s): QED42
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.