Contribution records
Contributors

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

Give credit to everyone
rfay rfay
matt2000 matt2000
webchick webchick
Cheek Cheek
agill agill
karens karens
sheilaj sheilaj
ahwebd ahwebd
cnolle cnolle
davegan davegan
mradcliffe mradcliffe
jcarlson34 jcarlson34
jcfiala jcfiala
alanburke alanburke
arianek arianek
naheemsays nbz
BogenDorpher BogenDorpher
plach plach
steinmb steinmb
mattbatt mattbatt
asb asb
eojthebrave eojthebrave
endrus endrus
betarobot betarobot
loganfsmyth loganfsmyth
eigentor eigentor
bfroehle bfroehle
droplet droplet
tcowin tcowin
Encarte Encarte
damienmckenna damienmckenna
zeezhao zeezhao
mikl mikl
varkenshand varkenshand
AlanAtLarge AlanAtLarge
markwittens markwittens
strellman strellman
Stol Stol
off OFF
bryancasler animelion
captaingeek captaingeek
pol Pol
moshe weitzman weitzman
Island Usurper islandusurper
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.