Contribution records
Contributors

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

Give credit to everyone
anybody Anybody organization(s): DROWL.de
abogomolov abogomolov
vierlex vierlex organization(s): acolono GmbH
dmsmidt MrDamasajaga organization(s): Synetic
xzuttz xzuttz
plopesc plopesc organization(s): Cocomore AG
betoissues betoissues
zero2one zero2one organization(s): Serial Graphics customer(s): District09
jeroent JeroenT organization(s): iO
markconroy MarkConroy organization(s): Annertech
jelle_s jelles
drcolossos DrColossos organization(s): Protobyte
soulreceiver SoulReceiver organization(s): Full Fat Things
tim_dj tim_dj organization(s): IBFD
basvredeling basvredeling organization(s): IBFD customer(s): IBFD
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
myst1c myst1c organization(s): Annertech
timohuisman timohuisman organization(s): SWIS
rhezios Rhezios organization(s): SWIS
a.milkovsky milkovsky
sense-design sense
arun ak ARUN
c.hoyer cahodk
john cook johncook organization(s): Cojolan customer(s): Annertech
giorgosk GiorgosK
eelkeblok eelkeblok organization(s): ronder
ikit-claw ikit-claw organization(s): Annertech
matthiasm11 matthiasm11
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.