Contribution records
Contributors

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

Give credit to everyone
legolasbo legolasbo volunteering
phiit phiit
xjm xjm
enhdless enhdless
parthipanramesh parthipanramesh
areke areke
jvranckx jvranckx
jgSnell jgsnell
dawehner dereine volunteering
xano Xano
taran2l Taran2L
damiankloip damiankloip
connorwk connorwk
martin107 martin107
amitgoyal amitgoyal
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
jhedstrom jhedstrom
mile23 Mile23
borisson_ borisson_ volunteering
jgeryk jgeryk
tkuldeep17 tkuldeep organization(s): Axelerant
steinmb steinmb volunteering
stuti.manandhar stuti.manandhar
bogdan khrupa bogdan_khrupa
joshi.rohit100 joshi.rohit100
pushpinderchauhan er.pushpinderrana
anish.a anish volunteering
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.