Contribution records
Contributors

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

Give credit to everyone
sun sun
catch catch
plach plach
David_Rothstein drothstein
webchick webchick
chx chx
ksenzee ksenzee
mcrittenden mcrittenden
seutje seutje
Bojhan bojhan
mfer mfer
dww dww
effulgentsia effulgentsia
casey casey
dries dries
Frando frando
jhodgdon jhodgdon
pwolanin pwolanin
jacine Jacine
aaron aaron
Crell Crell
fago fago
q0rban q0rban
scor scor
aspilicious aspilicious
rfay rfay
c960657 c960657
quicksketch quicksketch
yched yched
heine heine
johnalbin johnalbin
boris mann borismann
damien tournoud damz
dave reid davereid
sun.core sun.core
Everett Zufelt everettz
moshe weitzman weitzman
gábor hojtsy goba
david strauss straussd
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.