Contribution records
Contributors

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

Give credit to everyone
boobaa boobaa
Galt1069 Galt1069
willmoy willmoy
kaakuu kaakuu
marcp marcp
JanZ JanZ
pwolanin pwolanin
jhodgdon jhodgdon
mlncn mlncn
catch catch
marcingy marcingy
mustanggb akamustang
Starminder Starminder
karens karens
webchick webchick
tarzadon tarzadon
tomimikola tomimikola
rolfmeijer rolfmeijer
cweagans cweagans
chx chx
richardmetzger richardmetzger
xjm xjm
kathyh kathyh
RedRat RedRat
Shoffner Shoffner
michaelkoehne michaelkoehne
joaomachado joaomachado
Bastlynn bastlynn
avisconti amandavisconti
heddn lucashedding organization(s): MTech, LLC
denes.szabo denesszabo
dave reid davereid
albert volkman avolkman
gábor hojtsy goba
Sequencing.com Sequencing
priya.chat priya.chat organization(s): Publicis Sapient customer(s): Publicis Sapient
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.