Contribution records
Contributors

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

Give credit to everyone
David_Rothstein drothstein
sun sun
yoroy yoroy
kika kika
casey casey
eigentor eigentor
joachim joachim
EvanDonovan evandonovan
cha0s cha0s
mgifford mgifford
webchick webchick
effulgentsia effulgentsia
nod_ nod_
mcjim mcjim
geerlingguy geerlingguy
Bojhan bojhan
rachel_norfolk rachel_norfolk
tkoleary tkoleary
lisarex lisarex
robloach robloach
catch catch
saltednut saltednut
swentel swentel
aspilicious aspilicious
gmclelland gmclelland
lewisnyman lewisnyman
jessebeach jessebeach
thedavidmeister thedavidmeister
ksenzee ksenzee
dries dries
rooby rooby
owen barton grugnog
Everett Zufelt everettz
gábor hojtsy goba
wim leers wimleers
Jeff Burnz jmburnz
jp.stacey jpstacey
dave reid davereid
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.