Contribution records
Draft
Contributors

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

Give credit to everyone
yched yched
amateescu amateescu customer(s): Pfizer, Inc.
fago fago
jibran jibran
heddn lucashedding organization(s): Forum One, MTech, LLC
peri22 peri22 organization(s): Penceo
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
kfritsche kfritsche organization(s): bio.logis Genetic Information Management GmbH
hchonov hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
tstoeckler tstoeckler organization(s): bio.logis Genetic Information Management GmbH
gease gease organization(s): bio.logis Genetic Information Management GmbH
artemboiko artemboiko organization(s): EPAM customer(s): EPAM
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
smustgrave smustgrave organization(s): Mobomo
caesius caesius organization(s): Forum One
claudiu.cristea claudiucristea organization(s): Webikon
imre.horjan imre.horjan volunteering organization(s): Penceo
eric.chenchao cityreader
wim leers wimleers organization(s): Acquia
dave.mentens dave.mentens
tiagoz TiagoZ volunteering organization(s): JAVALI
pancho pancho
rkoller rkoller
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.