Contribution records
Contributors

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

Give credit to everyone
michelle Michelle
nancydru nancyw
Leeteq Leeteq
tonyn skiquel
lilou lilou
sun sun
juan_g juan_g
Bojhan bojhan
yched yched
int int
David_Rothstein drothstein
chx chx
dries dries
rfay rfay
webchick webchick
mertskeli mertskeli
ksenzee ksenzee
klonos klonos
pwolanin pwolanin
StuartJNCC StuartJNCC
effulgentsia effulgentsia
tstoeckler tstoeckler
rszrama rszrama
EvanDonovan evandonovan
sobi3ch sobi3ch
jhodgdon jhodgdon
davepoon davepoon
jn2 jn2
thedavidmeister thedavidmeister
Gurpartap Singh Gurpartap
dave reid davereid
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.