Contribution records
Contributors

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

Give credit to everyone
nod_ nod_
msonnabaum msonnabaum
jessebeach jessebeach
Shoseki Shoseki
lewisnyman lewisnyman
quicksketch quicksketch
rupl rupl
ao5357 ao5357
IceCreamYou2 IceCreamYou2
catch catch
rooby rooby
stolzenhain stolzenhain
bojanz bojanz
attiks attiks
mfer mfer
damienmckenna damienmckenna
JamesK jkenn99
sun sun
droplet droplet
eaton eaton
neclimdul neclimdul
MrMaksimize MrMaksimize
dmethvin dmethvin
cweagans cweagans
robloach robloach
donquixote donquixote
cosmicdreams cosmicdreams
rj rj
adamdicarlo adamdicarlo
webchick webchick
effulgentsia effulgentsia
edward_or eoriordan
zzolo zzolo
damien tournoud damz
paul.lovvik paullovvik
gábor hojtsy goba
frank ralf frankralf
sylvain lecoy SylvainLecoy
wim leers wimleers
riddhi.addweb Jigar.tanna
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.