Contribution records
Contributors

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

Give credit to everyone
quietone quietone volunteering
jofitz jofitz organization(s): ComputerMinds
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
pk188 pk188 organization(s): OpenSense Labs
mikeryan mikeryan volunteering organization(s): Virtuoso Performance
shashikant_chauhan shashikant volunteering organization(s): Iksula
maxocub maxocub volunteering
edysmp edysmp organization(s): MTech, LLC
tacituseu tacituseu
dhruveshdtripathi DhruveshTripathi organization(s): DevsAdda
wim leers wimleers organization(s): Acquia
gábor hojtsy goba organization(s): Acquia
pritishkumar pritish.kumar organization(s): OpenSense Labs
rakesh.gectcr rakeshjames volunteering organization(s): Valuebound customer(s): Acro Commerce
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.