Contribution records
Contributors

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

Give credit to everyone
ParisLiakos rootatwc
Makeitgo100 Makeitgo100
Branjawn Branjawn
dourouc05 dourouc05
adam_b adam_b
mrandr mrandr
shinz83 shinz83
yched yched
Paragon Paragon
mefisto75 mefisto75
blup blup
morleti morleti
janeks janeks
carlbowden carlbowden
jdleonard jdleonard
gmopinillosv gmopinillosv
rp7 rp7
catch catch
nilsx nils-m
bfroehle bfroehle
kenheim kenheim
johnv johnv
Leeteq Leeteq
chx chx
keha3912 keha3912
Starminder Starminder
sun sun
triple5 triple5
Cogito Cogito
dwalker51 dwalker51
g76 g76
perandre perandre
franklca franklca
bmx269 bmx269
effulgentsia effulgentsia
alanburke alanburke
tiagopb tiagopb
Solar75 Solar75
resveld resveld
David_Rothstein drothstein
cakka cakka
webankit babbar.ankit
damien tournoud damz
ryan.armstrong ryan.armstrong
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.