Contribution records
Contributors

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

Give credit to everyone
cortezj cortezj
kershme kershme
mgifford mgifford organization(s): OpenConcept Consulting Inc.
andrewmacpherson andrewmacpherson volunteering organization(s): Annertech
brenv brenv organization(s): Annertech
jofitz jofitz organization(s): ComputerMinds
droplet droplet
au_dave au_dave
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
tinto Tinto organization(s): The Savvy Few
rkoller rkoller
alexpott alexpott organization(s): Acro Commerce, Thunder
lendude Lendude volunteering organization(s): iO
smustgrave smustgrave organization(s): Mobomo
rajeshreeputra Rajeshreeputra volunteering organization(s): Acquia, Shivswarajya Inc.
lauriii lauriii organization(s): Acquia
himanshu-dixit himanshu-dixit volunteering
gaurav-mathur gaurav-mathur organization(s): Dotsquares Ltd.
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.