Contribution records
Contributors

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

Give credit to everyone
johnalbin johnalbin
Steven unconed
catch catch
seanr seanr
Hinrich hinrich
sumgai sumgai
webernet webernet
mikegulline mikegulline
tanc tanc
pwolanin pwolanin
troublehelix troublehelix
TheRec TheRec
GBain22 GBain22
domesticat domesticat
cburn cburn
AdrianB AdrianB
mgifford mgifford
RedTop RedTop
kangaroobin kangaroobin
chris_gooley chris_gooley
killua99 killua99
normal_orphan normal_orphan
stephaniefuda StephanieF
Daas Daas
snlnz snlnz
gynekolog gynekolog
dmkelner dmkelner
kilrizzy kilrizzy
netsensei netsensei
anybody Anybody organization(s): DROWL.de
Ryan Palmer rypalmer
Garrett Albright garrettalbright
Everett Zufelt everettz
Imaaxa-Cory Imaaxa-Cory
jason@greengeckodesign.com jason@greengeckodesign.com
wikki boy 03 wikki_boy_03
stephen Piscura stephen Piscura
nasi nasi
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.