Contribution records
Contributors

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

Give credit to everyone
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
bojanz bojanz organization(s): Centarro
mglaman mglaman
lisastreeter lisastreeter organization(s): Centarro
efpapado efpapado volunteering organization(s): Ramsalt Lab
nickvanboven nickvanboven volunteering
hockey2112 hockey2112
yonailo yonailo volunteering
cmcintosh cmcintosh organization(s): Wembassy llc customer(s): Wembassy llc
liquidcms liquidcms
devnyc devnyc
xamount xamount volunteering
ornagy ornagy
amateescu amateescu volunteering
mhawwari mhawwari organization(s): Vardot
mellowtothemax mellowtothemax
giorgosk GiorgosK
inwebsol inwebsol
benjarlett benjarlett
pslcbs pslcbs
socialnicheguru SocialNicheGuru
marciaibanez marciaibanez organization(s): CI&T
jsacksick jsacksick organization(s): Centarro
jmoruzi jmoruzi
kaipipek kaipiroska
fonant Fonant
s.messaris s.messaris
k.skarlatos KonstantinosSkarlatos volunteering organization(s): Pelagus Creative Web
jacob.embree jacob.embree organization(s): St. Louis Integration
mandus.cz martinpetracek.com
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.