Contribution records
Contributors

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

Give credit to everyone
eric_a erica
mkalkbrenner mkalkbrenner organization(s): bio.logis Genetic Information Management GmbH
hchonov hchonov volunteering organization(s): bio.logis Genetic Information Management GmbH
nick_vh nickvh organization(s): Dropsolid
andypost andypost volunteering organization(s): Skilld
mikelutz mdlutz volunteering organization(s): Four Kitchens, ICON Interactive
cspitzlay cspitzlay organization(s): bio.logis Genetic Information Management GmbH
mpp mpp organization(s): AmeXio Fuse customer(s): District09
xjm xjm
catch catch organization(s): Third and Grove
bojanz bojanz organization(s): Centarro
spokje Spokje organization(s): Annertech
karimb KarimB volunteering
trevorbradley TrevorBradley
jibran jibran volunteering
nicrodgers nicrodgers organization(s): Welsh Government
ecvandenberg ecvandenberg volunteering
berdir berdir organization(s): MD Systems GmbH
sam452 sam452 volunteering
Yanivs Yanivs volunteering
gábor hojtsy goba organization(s): Acquia
davide.porrovecchio davide.porrovecchio volunteering
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.