Contribution records
Contributors

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

Give credit to everyone
khad khad
Bilmar Bilmar
eugenmayer eugenmayer
fatfish fatfish
croryx croryx
izkreny izkreny
fanzila fanzila
matthewl matthewl
FooZee FooZee
sinasalek sinasalek
darrellduane DarrellDuane
georgwaechter georgwaechter
deggertsen deggertsen
Cliffy Cliffy
mshick mshick
pnx pnx
ohnobinki ohnobinki
bulldozer2003 briankpeterson
eriknewby eriknewby
yautja_cetanu yautja_cetanu
izmeez izmeez
richardmetzger richardmetzger
soulfroys soulfroys
jared_sprague jared_sprague
michelle Michelle
greggles greggles
AndreU AndreU
blackice2999 blackice2999
omaster omaster
fonant Fonant
spacerabbit spacerabbit
stacysimpson stacysimpson
binarydru binarydru
jncruces jncruces
neilt17 neilt17
Fidelix Fidelix
navi85sin navi85sin
kars-t karst
ñull com2
gregoire@inficiences.com gregoire-at-inficiences.com
manuel.adan adan
Robin Millette millette
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.