Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
valthebald
nexusnovaz volunteering organization(s): Zoocha
breidert
littlepixiez organization(s): Zoocha
dan2k3k4 organization(s): amazee.io customer(s): amazee.io
dunx organization(s): Zoocha
gantal organization(s): Elevated Third
salvatore_severo
bisonbleu
svendecabooter organization(s): Sven Decabooter customer(s): EntityOne, Dynamate
lussoluca organization(s): SparkFabrik
d34dman organization(s): Factorial.io, Digitwings
thejimbirch organization(s): Kanopi Studios
owenwilliams organization(s): Zoocha
b_sharpe organization(s): ImageX
robertoperuzzo
marcus_johansson organization(s): FreelyGive
kristen pol organization(s): Itty Bitty Byte, Salsa Digital
kim.pepper organization(s): PreviousNext
the_g_bomb
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
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.