Contribution records
Contributors

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

Give credit to everyone
hchonov hchonov volunteering organization(s): 1xINTERNET, bio.logis Genetic Information Management GmbH
ptmkenny ptmkenny
MaskOta MaskOta
aguilarm aguilarm
davidburns davidburns volunteering
yesct YesCT organization(s): Lullabot customer(s): IBM
tomefa tomefa volunteering
petu petu volunteering
gease gease organization(s): bio.logis Genetic Information Management GmbH
kalabro kalabro
wells wells organization(s): Cascade PBS
amateescu amateescu customer(s): Tag1 Consulting, Inc.
s_leu s_leu organization(s): Tag1 Consulting, Inc.
wranvaud wranvaud volunteering
wolcen wolcen organization(s): Agaric
phernand42 phernand42
staalex alex.stanciu organization(s): 1xINTERNET
nitin.k nitin.k volunteering
chr.fritsch chr.fritsch organization(s): Thunder
jan-e Jan-E
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.