Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen
longwave organization(s): Full Fat Things
carsteng organization(s): JAKALA (formerly FFW)
fkildoo
jshimota01
brewerkr
davidhk
nlisgo
philltran organization(s): Symmetri Technology
puregin organization(s): The Little Dev Shop Inc.
poker10 organization(s): ActivIT s.r.o.
ppound
arturopanetta
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
lendude organization(s): iO
danchadwick
catch organization(s): Third and Grove
david.qdoscc
freddy rodriguez volunteering organization(s): Coresis
Ankit.Gupta organization(s): Dotsquares Ltd.
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.