Contribution records
Contributors

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

Give credit to everyone
HS HS
dries dries
toddwoof toddwoof
yang_yi_cn yangyicn
deverman deverman
akahn akahn
anybody Anybody
stevehays stevehays
sgriffin sgriffin
MagicT MagicT
CosminCH CosminCH
himagarwal himagarwal
robertgarrigos robertgarrigos
avpaderno avpaderno volunteering
googletorp googletorp
juan_g juan_g
khan22 khan22
funana funana
abarrios abarrios
siamect siamect
kenyan kenyan
zazakis zazakis
EddieN120 EddieN120
gripmedia gripmedia
silverwing silverwing
vako vako
xmacinfo xmacinfo
jenlampton jenlampton
john_b John_B
Gastonia Gastonia
jhakasseo jhakasseo
sun sun
Mayaaa pooja
eshta lkhaas
nick_vh nickvh
Benjamin Schrauwen benjaminschrauwen
tamanna-freelancer tamanna
Walt Esquivel Walt_Esquivel
dave reid davereid
Jason Dean pushka
elijah lynn ElijahLynn
amir simantov AmirSimantov
Anderso-1 Anderso-1
Kyttaritida Kyttaritida
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.