Contribution records
Contributors

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

Give credit to everyone
alexpott alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
xjm xjm organization(s): Acquia, xjm
joachim joachim volunteering
andypost andypost volunteering organization(s): Skilld
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
mikelutz mdlutz volunteering
megachriz megachriz volunteering organization(s): WebCoo
phenaproxima phenaproxima organization(s): Acquia
benjifisher benjifisher organization(s): Isovera customer(s): Pegasystems
bojanz bojanz organization(s): Centarro
etroid Etroid
quietone quietone volunteering organization(s): PreviousNext
irinaz irinaz volunteering organization(s): Fibonacci Web Studio
gambry gambry organization(s): EPAM
bhanu951 Bhanu951 volunteering
smustgrave smustgrave organization(s): Mobomo
tim.plunkett tim.plunkett organization(s): Acquia
wim leers wimleers organization(s): Acquia
shubham.prakash shubham.prakash organization(s): OpenSense Labs
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.