Contribution records
Contributors

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

Give credit to everyone
jacine Jacine
nomonstersinme nomonstersinme
moonray moonray organization(s): Chapter Three (acquired by Kanopi Studios)
rfay rfay
WorldFallz worldfallz
jpw1116 jpw1116
esod esod
ChrisBryant chrisbryant
sun sun
sivaji_ganesh_jojodae sivaji
verta verta
tribe_of_dan tribe_of_dan
polishyourimage polishyourimage
danepowell danepowell
alberto56 alberto56
mbannach mbannach
drupizzle rlblake
esclapes esclapes
alexander allen AlexanderAllen
john franklin franklin
Melissamcewen melissamcewen
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.