Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
valthebald organization(s): Dropsolid
dunx organization(s): Zoocha
arisha organization(s): Zoocha
littlepixiez volunteering organization(s): Zoocha
udhaya kumar volunteering organization(s): UniMity Solutions Pvt Limited
bbruno organization(s): 1xINTERNET
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
dan2k3k4 organization(s): amazee.io, amazee.io
thejimbirch organization(s): Kanopi Studios
gantal organization(s): Elevated Third
owenwilliams organization(s): Zoocha
bisonbleu volunteering
scott_euser volunteering organization(s): Soapbox
nexusnovaz volunteering organization(s): Zoocha
unqunq volunteering organization(s): DigitalTrotter
svendecabooter organization(s): Sven Decabooter customer(s): EntityOne, Dynamate
a.dmitriiev organization(s): 1xINTERNET
d34dman volunteering organization(s): Factorial.io
marcus_johansson organization(s): FreelyGive
robertoperuzzo organization(s): SparkFabrik
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
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.