Contribution records
Contributors

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

Give credit to everyone
twod twod
clawz clawz
wthomas wthomas
hugh4 hugh4
david1409 david1409
miro_dietiker mirodietiker
jleinenbach jleinenbach
tars16 tars16
hedac hedac
unegro unegro
JThan JThan
nancydru nancyw
fabianx Fabianx
tnats tnats
SchwebDesign SchwebDesign
boftx boftx
mcarrera mcarrera
chaloalvarezj chaloalvarezj
locomo locomo
jazzun4141 jazzun4141
icyread icyread
Outtascope Outtascope
adrianmak adrianmak
euchrid9 euchrid9
BaliDave BaliDave
starbucksguy starbucksguy
nevosa nevos
CaptDan CaptDan
l4facc l4facc
aeternus aeternus
giorgosk GiorgosK
elBradford elBradford
aleksey.tk cyberpunk
Peter Thomassen Peter_Thomassen
danny englander danny-englander
Jiri Volf Jiri_Volf
tom.d tom.d
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.