Contribution records
Contributors

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

Give credit to everyone
chaseontheweb ChaseOnTheWeb
rudranil29 rudranil29s organization(s): Material
Waldoswndrwrld Waldoswndrwrld organization(s): iO
ankush_03 ankushgautm organization(s): Material customer(s): Material
diego_mow DiegoMow volunteering organization(s): CI&T
swatichouhan012 swatichouhan organization(s): Valuebound customer(s): Valuebound
rivimey rivimey volunteering organization(s): IvimeyCom
wundo wundo organization(s): Chuva Inc. customer(s): Galoa Science
berdir berdir organization(s): MD Systems GmbH
japerry japerry organization(s): Acquia
jigish.addweb jigish.addweb organization(s): AddWeb Solution Pvt. Ltd.
john cook johncook organization(s): Creode
suresh prabhu parkala SureshPrabhuParkala organization(s): Specbee
Git commit message
Commit types
  • 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

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.