Contribution records
Contributors

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

Give credit to everyone
pol Pol
nod_ nod_
jessebeach jessebeach
jcisio jcisio
pounard pounard
cweagans cweagans
tstoeckler tstoeckler
pwolanin pwolanin
andypost andypost
sun sun
damiankloip damiankloip
klonos klonos
webchick webchick
effulgentsia effulgentsia
xano Xano
alexpott alexpott
jhodgdon jhodgdon
longwave longwave
markhalliwell markcarver
mortendk mortendk
joelpittet joelpittet
rainbowarray RainbowArray
lewisnyman lewisnyman
naheemsays nbz
sdboyer sdboyer
benjy benjy
cilefen cilefen
jibran jibran
aspilicious aspilicious
dave reid davereid
tim.plunkett tim.plunkett
wim leers wimleers
moshe weitzman weitzman
star-szr star-szr
danny englander danny-englander
Jeff Burnz jmburnz
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.