Issue
Contribution records
Contributors

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

Give credit to everyone
bojanz organization(s): Centarro
franksj organization(s): Breakthrough Technologies, LLC
SchwebDesign
heddn organization(s): Acro Commerce, MTech, LLC
smccabe volunteering organization(s): Acro Commerce
joachim volunteering
brunodbo organization(s): Textillia
porchlight volunteering organization(s): Northern Commerce
jwjoshuawalker
andyg5000 organization(s): Blue Oak Interactive
bfuzze9898 volunteering
jonathanshaw
penyaskito
johnpitcairn
recidive organization(s): Centarro customer(s): Zivtech
andypost volunteering organization(s): Skilld
JeremyFrench organization(s): Full Fat Things
longwave organization(s): Full Fat Things
marthinal organization(s): Bluespark
arthur_lorenz organization(s): 1xINTERNET
jsacksick organization(s): Centarro customer(s): Matsmart
rinasek organization(s): Centarro
tbkot organization(s): Lemberg Solutions
phannphong volunteering organization(s): Athena, FIDESIO
zaporylie customer(s): Centarro
vetal4ik organization(s): DevBranch, Drupal Ukraine Community customer(s): Soapbox
a.dmitriiev organization(s): 1xINTERNET
emil stoianov volunteering
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.