Contribution records
Contributors

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

Give credit to everyone
OnkelTem onkeltem
chx chx
drewish drewish
c960657 c960657
webchick webchick
munzirtaha munzirtaha
hapydoyzer nao
Gozi Gozi
GoofyX lourdas_v
bloodmud bloodmud
kotnik kotnik
andypost andypost
sun sun
mikeytown2 mikeytown2
dhthwy dhthwy
wwwwoicn wwwwoicn
droplet droplet
catch catch
xlsoul xlsoul
xjm xjm
097633 097633
aaron aaron
caligan MarieWendel
realityloop realityloop
rogical rogical
gghchem gghchem
aspilicious aspilicious
biydng biydng
oriol_e9g oriole9g
nicxvan nicxvan
migimaru migimaru
damien tournoud damz
jean-philippe fleury Jean-Philippe_Fleury
Ivan Simonov ivansimonov
tim.plunkett tim.plunkett
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.