Issue
Contribution records
Contributors

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

Give credit to everyone
hchonov organization(s): bio.logis Genetic Information Management GmbH
quietone volunteering
mikeryan volunteering organization(s): Virtuoso Performance
kerasai organization(s): myDropWizard
bucefal91 organization(s): Websolutions Agency
heddn organization(s): Acro Commerce, MTech, LLC
rpayanm organization(s): Kadabra
rp7 customer(s): Government of Flanders
partdigital
robertshell22
solenity
josephdpurcell organization(s): Bounteous
grimreaper organization(s): Smile
super_romeo volunteering
rob_pr
jebschiefer
radelson organization(s): WebstanZ
pfrenssen customer(s): European Commission and European Union Institutions, Agencies and Bodies
jeroen.b organization(s): .VDMi/
a.dmitriiev organization(s): 1xINTERNET
moshe weitzman
seth.e.shaw
james.williams organization(s): ComputerMinds
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.