Contributors

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

Give credit to everyone
jgjg jgjg
yashaswi18 Yashaswi18
scott_euser scotteuser volunteering organization(s): Soapbox
johnatas johnatas organization(s): Klee Interactive (Klee Group)
kobusvw kobusvw
istankevych elias volunteering organization(s): Trembita Digital
hydra Hydra volunteering organization(s): erdfisch
ckng ckng
rkelbel48 kibble48 organization(s): City of Hope
charlliequadros charlliequadros volunteering organization(s): Zoocha
jsutta jsutta
nessthehero nessthehero
s3b0un3t S3b0uN3t
svenryen svenryen organization(s): Ramsalt Lab
jurgenhaas jurgenhaas organization(s): LakeDrops
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.