Issue
Contribution records
Contributors

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

Give credit to everyone
jofitz organization(s): ComputerMinds
MerryHamster organization(s): Skilld
msankhala volunteering organization(s): Material
surbz organization(s): Material
andypost volunteering organization(s): Skilld
zeip organization(s): Citrus Solutions Oy customer(s): City of Pori
boaloysius volunteering organization(s): Google Summer of Code
darrenwh volunteering
ritzz organization(s): Valuebound
tameeshb organization(s): Google Summer of Code
wturrell
xjm organization(s): Acquia
alexpott organization(s): Acro Commerce
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
Yasiru Nilan
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.