Contribution records
Draft
Contributors

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

Give credit to everyone
ifrik ifrik
mgifford mgifford organization(s): OpenConcept Consulting Inc.
mpdonadio matthew.donadio organization(s): DiD Agency
ok_lyndsey ok_lyndsey volunteering
kreatil kreatIL volunteering
andrezstar andrezstar
merilainen mErilainen organization(s): Mearra (formerly known as Wunder)
frederickjh frederickjh
jonathan1055 jonathan1055 volunteering
colan colan organization(s): Consensus Enterprises customer(s): OCASI
vacho vacho organization(s): Skilld
elek elek02
ressa ressa organization(s): Ardea
xmacinfo xmacinfo organization(s): xMac info
joachim joachim volunteering
lomale@bluewin.ch istdp_webmaster volunteering
david.qdoscc qdoscc
arx-e arx-e
jaime@gingerrobot.com jaimekristene organization(s): Ginger Robot
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.