Contribution records
Contributors

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

Give credit to everyone
martin_klima martin_klima
alexpott alexpott organization(s): Acro Commerce, Thunder
megachriz megachriz organization(s): WebCoo
mattjones86 mattjones86
k4v k4v volunteering
darrenwh darrenwh volunteering organization(s): Investis Digital
ocastle ocastle organization(s): Full Bundle
santimg santimg
dunebl dunebaud
jungle jungle volunteering
spokje Spokje volunteering
phenaproxima phenaproxima organization(s): Acquia
ornagy ornagy
daffie daffie
jurgenhaas jurgenhaas organization(s): LakeDrops, PARAGON Executive Services GmbH
john.nie John-lee volunteering
mario steinitz MarioSteinitz organization(s): SHORELESS Limited
m.lebedev m.lebedev
jian he jianhe
adam clarey rabbit_media
abhijith s AbhijithS volunteering organization(s): Zyxware Technologies
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.