Contribution records
Contributors

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

Give credit to everyone
murz murz
rkendall rkendall
kreynen kreynen
techczech techczech
IcyAndy IcyAndy
domasj domasj
charles_elwood charles_elwood
kpaul kpaul
modoq modoq
kckern kckern
keesje keesje76
simontol simontol
ekendra ekendra
fm fm
ilbeppe ilbeppe
gellpak gellpak
Wutimer DavidW
Devis Devis
sdub sdub
wildtang3nt wildtang3nt
dropcube dropcube
mikeryan mikeryan
janeri janeri
akie akie
ogi ogi
physiotek physiotek
alaa alaa
xcorex xcorex
izmeez izmeez
yogi_sydbma CaptainKranq
John_0 John_0
Jamie Holly HollyIT
Steve Dondley steved
boris mann borismann
anuradha-1 anuradha-1
-hgn- -hgn-
piero.giobbi piero.giobbi
owen barton grugnog
Beau Gunderson Beau Gunderson
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.