Contribution records
Contributors

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

Give credit to everyone
kmajzlik karlos007 organization(s): Ciklum Western Europe
mpp mpp organization(s): AmeXio Fuse customer(s): District09
Derimagia dwikoff organization(s): Mindgrub Technologies
aburrows abdesignuk organization(s): DigiDrop
andrewmacpherson andrewmacpherson volunteering organization(s): Annertech
cferthorney cferthorney volunteering organization(s): Annertech
botris botris
jcmartinez jcmartinez volunteering
xurizaemon xurizaemon organization(s): Catalyst IT
Marijn82 Marijn82
fabienly fabienly volunteering
ericmaster ericmaster volunteering
marvil07 marvil07 organization(s): Adapt
bthiemenatlaw BThiemeNatlaw
freed_paris freed_paris
greg.1.anderson greg1anderson organization(s): Pantheon
andres.torres antrecu
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.