Contribution records
Contributors

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

Give credit to everyone
mibfire mibfire
twod twod
marktheshark marktheshark
lsolesen lsolesen
AvalancheOfLlamas AvalancheOfLlamas
lotyrin lotyrin
rocketeerbkw rocketeerbkw
saltednut saltednut
dooleysarahe dooleysarahe
guillaumev guillaumev
jrglasgow jrglasgow
rodricels rodricels
RunePhilosof RunePhilosof
pjbarry21 pjbarry21
sylus sylus
kunago kunago
dmsmidt MrDamasajaga
dddbbb danbohea
drupov mrupal
elstudio elstudio
kerasai bmoresafety20
jeffdiecks jeffdiecks
damienmckenna damienmckenna
deggertsen deggertsen
arosboro arosboro
spgd01 spgd01
alexmc alexmc
imclean imclean
samwillc samwillc
pdcrane pdcrane
tjtj tjtj
jerry jerry
kenorb kenorb
person101x person101x
sadashiv sadashiv
eric.chenchao cityreader
k.skarlatos KonstantinosSkarlatos
green monkey green monkey
suzanne.aldrich aigeanta
hass hass
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.