Contribution records
Contributors

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

Give credit to everyone
chx chx organization(s): Integral Vision Ltd
benjy benjy organization(s): PreviousNext
imiksu iMiksu volunteering organization(s): Mearra (formerly known as Wunder)
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
nevergone nevergone
jofitz jofitz organization(s): ComputerMinds
maxocub maxocub volunteering
mohit1604 MohitMalik organization(s): Google Summer of Code
jgrunert jgrunert organization(s): Acro Commerce
SilviuChingaru SilviuChingaru organization(s): MagazinulCuScule.ro customer(s): MagazinulCuScule.ro
phenaproxima phenaproxima organization(s): Acquia
alexpott alexpott
catch catch organization(s): Third and Grove
gábor hojtsy goba organization(s): Acquia
dylan donkersgoed DylanDonkersgoed organization(s): Northern Commerce
bendeguz.csirmaz bendeguz.csirmaz organization(s): Cheppers
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.