Contribution records
Draft
Contributors

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

Give credit to everyone
add1sun add1sun
nicxvan nicxvan
mcannon mcannon
ali_tareque ali_tareque
generalconsensus generalconsensus
Brolag Brolag
fureigh fureigh
rkeller rkeller
timmvt timmvt
rainbowarray RainbowArray
bowevil Bowevil
oheller oheller
andileco andileco
cs_shadow cs_shadow
marcosdr marcosdr
srikanthk16 srikanthk16
zealfire zealfire
peterjlord plord
aphickey aphickey
nicoleheard nicoleheard
ssova ssova
Lord_of_Codes Lord-of-Codes
sudhanshug sudhanshug
joyceg joyceg organization(s): Google Code-In, Google Summer of Code
cryt1c Cryt1c
akashkrishnan01 akashfoss organization(s): Google Summer of Code
franciscojlucero frank7997 volunteering
jayly jayly
anhtq 0wl organization(s): Google Code-In
ragasirtahk ragasirtahk organization(s): Google Code-In
Percy101 Percy101 volunteering
Akif Khan akif500 akif500
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.