Contribution records
Contributors

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

Give credit to everyone
mgifford mgifford
casey casey
Bojhan bojhan
ksenzee ksenzee
David_Rothstein drothstein
jhodgdon jhodgdon
EvanDonovan evandonovan
dmitrig01 dmitrig01
develcuy develCuy
eigentor eigentor
cliff Cliff
tstoeckler tstoeckler
webchick webchick
bowersox brandonojc
yesct YesCT
aspilicious aspilicious
bleen bleen18
kaakuu kaakuu
avpaderno avpaderno
jasonkiss jasonkiss
marvil07 marvil07
bjcool bjcool
shunting shunting
attiks attiks
seutje seutje
catch catch
dries dries
Everett Zufelt everettz
owen barton grugnog
moshe weitzman weitzman
Chas Belov Chas_Belov
Jeff Burnz jmburnz
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.