Contribution records
Draft
Contributors

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

Give credit to everyone
karens karens
capellic capellic
alistairmcclymont alistairmcclymont
amcc amcc
cpelham cpelham
biohabit biohabit
tanc tanc
ericm ericm
FoolsRun FoolsRun
cedrix cedrix
laryn laryn
orbgasm orbgasm
plach plach
kepford kepford
trackleft trackleft
TimG1 TimG1
wuf31 wuf31
philsward philsward
sifuhall sifuhall
davidteall davidteall
giggler giggler_git
will_in_wi willinwi
muka muka
BenK benk
raspberryman raspberryman
YK85 YK85
rbrownell ryanbrownell
amogiz amogiz
kgg kgg
frodopwns frodopwns
undersound3 undersound3
kreatil kreatIL
knalstaaf knalstaaf
inversed inversed
hot_sauce hotsaucedesign
jmuzz muzzl
amh5514 ant-man
jproctor jproctor
Matthew Davidson mjd
Tony Sharpe Tony-S
Rob T Rob_T
random.op random.op
sean porter sean_porter
shiraz dindar Shiraz
weblance weblance
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.