Contribution records
Contributors

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

Give credit to everyone
vm vm
asb asb
sutharsan sutharsan
authentictech authentictech
jpdaley jpdaley
RockSoup rocksoup
kdebaas kdebaas
vegemite4me vegemite4me
mbeenon mbeenon
tomgf tom
RdN RdN
crutch crutch
patrickharris patrickharris
mybinaryromance mybinaryromance
j0e j0ey
akalata akalata
jawbreak jawbreak
hermes_costell hermes_costell
j0rd j0rd
RichardLynch RichardLynch
bushman bushman
13rac1 eosrei
theoracleprodigy theoracleprodigy
dsteplight dsteplight
Garrett Albright garrettalbright
justin.hopkins justin.hopkins
glass.dimly glassdimly
Alex Andrascu alexandrascu
Pascal.s Pascal.s
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.