Contribution records
Contributors

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

Give credit to everyone
dww dww
gateone panatlantica
modctek modctek
catch catch
pwolanin pwolanin
pasqualle pasqualle
kbahey kbahey
johnalbin johnalbin
Crell Crell
KingMoore kingmoore
BioALIEN BioALIEN
aclight aclight
webchick webchick
petey318 petey318
chx chx
ica ica
aslamc aslamc
sun sun
fk fk
beautifulmind beautifulmind
mattyoung mattyoung
scottbothel scottbothel
szb100 szb100
mikejoconnor mikejoconnor
lotyrin lotyrin
yoroy yoroy
yesct YesCT
marcingy marcingy
mustanggb akamustang
wretched sinner - saved by grace wretched_sinner_saved_by_grace
gábor hojtsy goba
MichaelK-1 MichaelK-1
Paul Natsuo Kishimoto khaeru
damien tournoud damz
sun.core sun.core
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.