Contribution records
Contributors

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

Give credit to everyone
mherchel mherchel
bojanz bojanz
ogi ogi
johnv johnv
zabelc zabelc
michielnugter michielnugter
dawehner dereine
sun sun
clashar clashar
merlinofchaos merlinofchaos
joachim joachim
Remon rgeorgy
gloomcheng gloomcheng
u8915055 u8915055
yellowhousedesign yellowhousedesign
Shadlington Shadlington
gg4 double
zzolo zzolo
jerdavis jerdavis
geerlingguy geerlingguy
marcoka eanima
Sylense Sylense
mstrelan mstrelan
trevorbradley TrevorBradley
JGonzalez JGonzalez
sachbearbeiter sachbearbeiter
that0n3guy that0n3guy
vasike vasike
basicmagic.net basicmagic.net
eric.chenchao cityreader
Stefan Haas Stefan Haas
ilya.bezdelev ilya.bezdelev
honza pobořil bobik
Git commit message
Commit types
  • 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

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.