Contribution records
Contributors

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

Give credit to everyone
David_Rothstein drothstein volunteering
wturrell wturrell volunteering
pk188 pk188 organization(s): OpenSense Labs
berdir berdir organization(s): MD Systems GmbH
jeffam jeffam organization(s): Cornell University
manojithape manojithape organization(s): QED42 customer(s): Drupal India Association
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
quietone quietone organization(s): PreviousNext
shortspoken moritzpeikert organization(s): werk21
ameymudras mudrasamey organization(s): Salsa Digital
catch catch organization(s): Third and Grove
sourabh.singhal sourdrup volunteering organization(s): Faichi Solutions Pvt Ltd customer(s): Faichi Solutions Pvt Ltd
krina.addweb krina.soni organization(s): AddWeb Solution Pvt. Ltd.
stefan.r stefan.r
dhirendra.mishra dhirendramishra10 organization(s): Valuebound customer(s): Valuebound
asha nair asha_nair organization(s): Zyxware Technologies
Manibharathi E R Manibharathi_E_R organization(s): Material customer(s): Material
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.