Contribution records
Contributors

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

Give credit to everyone
pwolanin pwolanin
rszrama rszrama
xurizaemon xurizaemon
univate univate
md2 markdavies
andreiashu andreiashu
cedarm cedarm
agileware agileware
stevendeporre stevendeporre
xibun xibun
redben redben
chellman chellman
lonelyrobot lonelyrobot
Bilmar Bilmar
EvanDonovan evandonovan
giorgio79 giorgio79
canuckistani canuckistani
drasgardian drasgardian
evanbarter evan
YK85 YK85
mstrelan mstrelan
tr tr
jeffschuler jeffschuler
fenstrat fenstrat
willieseabrook willieseabrook
gausarts gausarts
Daveydo Daveydo
MadOverlord MadOverlord
fchandler fchandler
bocaj bocaj
jerry jerry
geerlingguy geerlingguy
glennpratt glennpratt
hjelkris hjelkris
wwwoliondorcom wwwoliondorcom
bunset bunset
Island Usurper islandusurper
robby.smith robby.smith
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.