Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
vrancje organization(s): Liip
akrabat
ayalon
berdir organization(s): MD Systems GmbH
borisson_ organization(s): Calibrate customer(s): Acerta
ckrina organization(s): Lullabot
colorfield organization(s): amazee.io
dan2k3k4 organization(s): amazee.io
dasjo volunteering organization(s): Liip
dbu
drewmelck
guzmanb
hilletob
itamair volunteering
lammensj organization(s): Dropsolid
lukasfischer
lussoluca organization(s): SparkFabrik
michimauch
miro_dietiker organization(s): MD Systems GmbH
mkoh
pivica organization(s): MD Systems GmbH
schnitzel organization(s): amazee.io
wouters_f organization(s): Dropsolid
imre gmelig meijling volunteering organization(s): React online
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.