Contribution records
Contributors

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

Give credit to everyone
burningdog burningdog
jlevy jlevy
colin_young colin_young
kussmaul kussmaul
merlinofchaos merlinofchaos
karens karens
enboig enboig
coreyp_1 coreyp1
dawehner dereine
lunaris lunaris
lonelyrobot lonelyrobot
tpryor tpryor
ISPTraderChris ISPTraderChris
dagmar dagmar
SeanBannister seanbannister
swellbow swellbow
seabrawk seabrawk
PRZ PRZ
valderama valderama
dixon_ dixon
bendiy bendiy
Bilmar Bilmar
4drian 4drian
markus_petrux markuspetrux
vistree vistree
rjivan rjivan
Scott Reynolds scottreynolds
killes@www.drop.org killes
aren cambre arencambre
jason.fisher jason.fisher
Git commit message
Commit types
  • 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

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.