Contribution records
Contributors

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

Give credit to everyone
catch catch organization(s): Third and Grove
pounard pounard
sun sun
fago fago
fubhy sumsi
podarok podarok
xjm xjm
berdir berdir organization(s): MD Systems GmbH
effulgentsia effulgentsia
damiankloip damiankloip
jhedstrom jhedstrom organization(s): Phase2
andypost andypost volunteering
mile23 Mile23
eclipsegc eclipsegc
JvE JvE organization(s): One Shoe
amateescu amateescu customer(s): Pfizer, Inc.
hchonov hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
alexpott alexpott organization(s): Acro Commerce, Thunder
sam152 sam volunteering organization(s): PreviousNext
tacituseu tacituseu
mxh hauptm volunteering organization(s): Hubert Burda Media
alan d. aland
moshe weitzman weitzman
claudiu.cristea claudiucristea volunteering organization(s): Webikon
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.