Contribution records
Contributors

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

Give credit to everyone
jonlhouse jonlhouse
mauritsl mauritsl
andrebonfanti hohl
TimelessDomain TimelessDomain
ozsi ozsi
hedley hedley
pedrosp pedrosanchezpernia
drew29 drew29
joelrotelli joelrotelli
pardalman pardalman
XmhO XmhO
RKopacz RKopacz
aalireza aalireza
deanflory deanflory
therobyouknow therobyouknow
fantom84 fantom84
adam7 adam7
gmario gmario
bburg johnbburg
gildir gildir
mach5_kel mach5_kel
dtarc dtarc
Knud Knud
sinasalek sinasalek
Sigvard Sigvard
jaydee1818 jaydee1818
chilic chilic
yannickoo yannickoo
doxigo doxigo
jonraedeke jonraedeke
BarisW barisw
alibama alibama
dajka dajka
kopeboy kopeboy
NikGleb NikGleb
jOksanen Souless
ezoulou ezoulou
mahipal46 mahipal46 volunteering
dtabach dtabach
erik seifert erikseifert
JRZ-2 JRZ-2
phamkhaclam90@gmail.com lampk
esculcar esculcar
ivnish ivnish 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.