Contribution records
Contributors

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

Give credit to everyone
pwolanin pwolanin
Zothos Zothos
BioALIEN BioALIEN
ChrisKennedy chriskennedy
bjaspan bjaspan
m3avrck m3avrck
catch catch
coupet coupet
jaydub jaydub
dmitrig01 dmitrig01
dries dries
JirkaRybka JirkaRybka
nancydru nancyw
chx chx
klando klando
FiReaNGeL fireang3l
webchick webchick
CorniI corni
SteveR SteveR
AjK karpuz
fractile81 fractile81
yched yched
pancho pancho
hswong3i hswong3i
sammos sammoscheck
sinmao sinmao
moshe weitzman weitzman
david strauss straussd
scott.mclewin smclewin
gábor hojtsy goba
hass hass
Git commit message
Commit types
  • 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

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.